Need help with other JFrog products?
JFrog Enterprise+
JFrog Mission Control
JFrog Xray
JFrog Distribution
JFrog Pipelines
JFrog Bintray
JFrog Access
JFrog CLI
The Artifactory Generic Upload pipe uploads your generated build artifact(s) from the local file system to an Artifactory repository.
The task triggers JFrog CLI to perform the upload in the background.
The artifacts to upload may be defined using File Specs. By default, the pipe will also capture build-info and publish it to Artifactory as metadata associated with the uploaded file.
When configuring the pipe you must specify:
Code Block | ||||
---|---|---|---|---|
| ||||
# Upload artifacts to Artifactory - pipe: JfrogDev/artifactory-generic-upload:0.2.11 variables: ARTIFACTORY_URL: $ARTIFACTORY_URL ARTIFACTORY_USER: $ARTIFACTORY_USER ARTIFACTORY_PASSWORD: $ARTIFACTORY_PASSWORD FILE_SPEC: "false" SOURCE_PATH: "generic/*.zip" TARGET_PATH: "generic-local/" BUILD_NAME: "generic-pipe-example" |
See the pipe's README.md for the full list of variables you may specify.
The Artifactory Generic Download pipe downloads your built artifact(s) from an Artifactory repository to the local file system.
The task triggers JFrog CLI to perform the upload in the background.
The artifacts to download may be defined using File Specs. By default, the pipe will also capture build-info published to Artifactory as metadata associated with the downloaded file.
When configuring the pipe you must specify:
Code Block | ||||
---|---|---|---|---|
| ||||
# Download artifacts from Artifactory - pipe: JfrogDev/artifactory-generic-download:0.2.11 variables: ARTIFACTORY_URL: $ARTIFACTORY_URL ARTIFACTORY_USER: $ARTIFACTORY_USER ARTIFACTORY_PASSWORD: $ARTIFACTORY_PASSWORD FILE_SPEC: "false" SOURCE_PATH: "generic-local/*.zip" TARGET_PATH: "./generic/" BUILD_NAME: "generic-pipe-example" |
See the pipe's README.md for the full list of variables you may specify.
You can trigger the following builds.
TBD
TBD
The Artifactory Maven pipe triggers a Maven build, while resolving Maven dependencies and deploying Maven packages from and to Artifactory as a Maven repository.
By default, this pipe will also capture build-info and publish it to Artifactory as metadata associated with the built artifacts.
When configuring the pipe you must specify:
Code Block | ||||
---|---|---|---|---|
| ||||
# Build and publish Maven packages to Artifactory
- pipe: JfrogDev/artifactory-maven:0.2.9
variables:
ARTIFACTORY_URL: $ARTIFACTORY_URL
ARTIFACTORY_USER: $ARTIFACTORY_USER
ARTIFACTORY_PASSWORD: $ARTIFACTORY_PASSWORD
MAVEN_SNAPSHOT_REPO: "libs-snapshot"
MAVEN_RELEASE_REPO: "libs-release"
BUILD_NAME: "maven-pipe-example"
EXTRA_BAG_ARGS: "../" |
See the pipe's README.md for the full list of variables you may specify.
The Artifactory Maven pipe triggers a Maven build, while resolving Maven dependencies and deploying Maven packages from and to Artifactory as a Maven repository.
By default, this pipe will also capture build-info and publish it to Artifactory as metadata associated with the built artifacts.
When configuring the pipe you must specify:
Code Block | ||||
---|---|---|---|---|
| ||||
# Publish NPM package to Artifactory
- pipe: JfrogDev/artifactory-npm:0.2.3
variables:
ARTIFACTORY_URL: $ARTIFACTORY_URL
ARTIFACTORY_USER: $ARTIFACTORY_USER
ARTIFACTORY_PASSWORD: $ARTIFACTORY_PASSWORD
NPM_COMMAND: "publish"
NPM_TARGET_REPO: "npm-local"
BUILD_NAME: "npm-pipe-example" |
See the pipe's README.md for the full list of variables you may specify.
The Artifactory Docker pipe pushes a docker image to a docker repository in Artifactory.
By default, this pipe will also capture build-info and publish it to Artifactory as metadata associated with the docker image. In addition to details about the build and the build environment, the build info includes the image layers as build dependencies and build artifacts.
When configuring the pipe you must specify:
Code Block | ||||
---|---|---|---|---|
| ||||
# Build and publish Docker image to Artifactory
- pipe: JfrogDev/artifactory-docker:0.2.11
variables:
ARTIFACTORY_URL: $ARTIFACTORY_URL
ARTIFACTORY_USER: $ARTIFACTORY_USER
ARTIFACTORY_PASSWORD: $ARTIFACTORY_PASSWORD
DOCKER_IMAGE_TAG: "art-docker.mycompany.team/docker-pipe-example:${BITBUCKET_BUILD_NUMBER}"
DOCKER_TARGET_REPO: "docker-stage-local"
BUILD_NAME: "docker-pipe-example" |
See the pipe's README.md for the full list of variables you may specify.
To support the artifacts life-cycle, Artifactory supports promoting published builds from one repository to another.
The Artifactory Build Promotion pipe promotes a build, by either copying or moving the build artifacts and/or dependencies to a target repository.
This task can be added as part of a Build or Release pipeline.
When configuring the pipe you must specify:
The Artifactory repository to receive the promoted build's artifacts
The status message to set during promotion.
Other pipe options, such as a build name to associate with the promoted build.
Code Block | ||||
---|---|---|---|---|
| ||||
# Promote Build in Artifactory
- pipe: JfrogDev/artifactory-build-promotion:0.2.10
variables:
ARTIFACTORY_URL: $ARTIFACTORY_URL
ARTIFACTORY_USER: $ARTIFACTORY_USER
ARTIFACTORY_PASSWORD: $ARTIFACTORY_PASSWORD
TARGET_REPO: "npm-prod-local"
STATUS: "Staged"
BUILD_NAME: "npm-pipe-example" |
See the pipe's README.md for the full list of variables you may specify.
The Artifactory Xray Scan pipe triggers a build scan with JFrog Xray.
When the scan is triggered, Artifactory will pass on the build to Xray, which will then scan the build artifacts. The action is synchronous, meaning it will wait for the scan to finish before returning control to the script.
If the Allow fail build task option is set and Xray is configured to fail the build, the build pipeline will fail, if vulnerabilities are found.
When configuring the pipe you must specify:
Other pipe options, such as the name of the build to scan.
Code Block | ||||
---|---|---|---|---|
| ||||
# Scan published build through Xray
- pipe: JfrogDev/artifactory-xray-scan:0.2.7
variables:
ARTIFACTORY_URL: $ARTIFACTORY_URL
ARTIFACTORY_USER: $ARTIFACTORY_USER
ARTIFACTORY_PASSWORD: $ARTIFACTORY_PASSWORD
BUILD_NAME: "npm-pipe-example" |
See the pipe's README.md for the full list of variables you may specify.