Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Overview

Artifactory brings continuous integration to Atlassian Bitbucket Pipelines through the JFrog Artifactory pipes. 

 The JFrog Artifactory pipes for Bitbucket Pipelines supports:

  • Resolving your build dependencies from Artifactory. 
  • Deploying your build artifacts to Artifactory. 
  • Gaining full traceability of your builds by capturing your build-info from your builds and publishing to Artifactory.

About Pipes

Pipes are Atlassian’s way to simplify configuring your Bitbucket Pipeline. They’re very useful for frequently performed actions that would otherwise take several lines of script, especially when working with a supporting tool like Artifactory or Xray.

Just like a subroutine or object method in code, you invoke a pipe to perform a specific function according to parameters you provide.



Installation and Setup

No special setup is needed to use JFrog Artifactory pipes. They are readable in a public Bitbucket repository. You can select them, along with all other Atlassian-supported pipes, through the Bitbucket online editor, in the rightmost side panel.



Prerequisites

To use JFrog Artifactory pipes, you will need a licensed installation of Artifactory, and to know its addressable URL, and your credentials for access.

How a pipe works

In the YAML file that configures your Bitbucket Pipeline, you specify a path to the pipe, followed by a few key pieces of information.

Selecting one of the available pipes will present you the information from the pipe's README.md that you will need to put it to use.


To use a pipe in a Bitbucket Pipeline, copy the offered snippet to the Bitbucket YAML file, and replace the placeholder parameter text with the needed information. A best practice is to reference commonly needed parameters, such the base Artifactory URL, and your credentials, as environment settings.


For more information about Build Info, see Artifactory Build Integration.


Page Contents

Upload Generic Artifacts to Artifactory

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:

  1. Your Artifactory service URL
  2. Your credentials
  3. Whether you will use a File Spec or directly specify the artifact(s) to upload.
  4. The path to the artifcact(s) to upload (wild cards may be used), or the path to the File Spec.
  5. The target path of the Artifactory repository that will receive the upload.
  6. Other pipe options, such as a build name to associate with the artifact.
Example: Upload generic artifacts to Artifactory
# 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.

Downloading Generic Artifacts from Artifactory

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:

  1. Your Artifactory service URL
  2. Your credentials
  3. Whether you will use a File Spec or directly specify the artifact(s) to download.
  4. The source path of the Artifactory repository where the file to download is stored. You may use wildcards to specify multiple artifacts.
  5. Other pipe options, such as the local file system target path for the downloaded artifact.
Example: Download generic artifacts from Artifactory
# 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.

Triggering Builds

You can trigger the following builds.

Triggering Maven Builds

TBD

Triggering Npm Builds

TBD

Pushing and Pulling Docker Images to and from Artifactory


Promoting Published Builds in Artifactory

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.

Scanning Published Builds with JFrog Xray


Overview

Artifactory brings continuous integration to Atlassian Bitbucket Pipelines through the JFrog Artifactory pipes. 

 The JFrog Artifactory pipes for Bitbucket Pipelines supports:

  • Resolving your build dependencies from Artifactory. 
  • Deploying your build artifacts to Artifactory. 
  • Gaining full traceability of your builds by capturing your build-info from your builds and publishing to Artifactory.

About Pipes

Pipes are Atlassian’s way to simplify configuring your Bitbucket Pipeline. They’re very useful for frequently performed actions that would otherwise take several lines of script, especially when working with a supporting tool like Artifactory or Xray.

Just like a subroutine or object method in code, you invoke a pipe to perform a specific function according to parameters you provide.



Installation and Setup

No special setup is needed to use JFrog Artifactory pipes. They are readable in a public Bitbucket repository. You can select them, along with all other Atlassian-supported pipes, through the Bitbucket online editor, in the rightmost side panel.



Prerequisites

To use JFrog Artifactory pipes, you will need a licensed installation of Artifactory, and to know its addressable URL, and your credentials for access.

How a pipe works

In the YAML file that configures your Bitbucket Pipeline, you specify a path to the pipe, followed by a few key pieces of information.

Selecting one of the available pipes will present you the information from the pipe's README.md that you will need to put it to use.


To use a pipe in a Bitbucket Pipeline, copy the offered snippet to the Bitbucket YAML file, and replace the placeholder parameter text with the needed information. A best practice is to reference commonly needed parameters, such the base Artifactory URL, and your credentials, as environment settings.


Page Contents

Upload Generic Artifacts to Artifactory

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:

  1. Your Artifactory service URL
  2. Your credentials
  3. Whether you will use a File Spec or directly specify the artifact(s) to upload.
  4. The path to the artifcact(s) to upload (wild cards may be used), or the path to the File Spec.
  5. The target path of the Artifactory repository that will receive the upload.
  6. Other task options, such as a build name to associate with the artifact.


Upload generic artifacts to Artifactory
# 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.

Downloading Generic Artifacts from Artifactory

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 

The Artifactory Generic Upload pipe uploads your generated build artifact(s) from the local file system to Artifactory. 

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:

  1. Your Artifactory service URL
  2. Your credentials
  3. Whether you will use a File Spec or directly specify the artifact(s) to upload.
  4. The path to the artifcact(s) to upload (wild cards may be used), or the path to the File Spec.
  5. The target path of the Artifactory repository that will receive the upload.
  6. Other task options, such as a build name to associate with the artifact.

capture build-info and publish it to Artifactory as metadata associated with the uploaded file. 

When configuring the pipe you must specify:

  1. Your Artifactory service URL
  2. Your credentials
  3. Whether you will use a File Spec or directly specify the artifact(s) to upload.
  4. The path to the artifcact(s) to upload (wild cards may be used), or the path to the File Spec.
  5. The target path of the Artifactory repository that will receive the upload.
  6. Other task options, such as a build name to associate with the artifact.

For more information about Build Info, see Artifactory Build Integration.

Triggering Builds

You can trigger the following builds.

Triggering Maven Builds

TBD

Triggering Npm Builds

TBD

Pushing and Pulling Docker Images to and from Artifactory


Promoting Published Builds in Artifactory

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.

Scanning Published Builds with JFrog Xray


  • No labels