Table of Contents

• Overview
• Installing and configuring the plugin
• Configuring JFrog CLI as a Tool
  • Automatic installation from release.jfrog.io
  • Automatic installation from Artifactory
  • Manual installation
• Using JFrog CLI in your pipeline jobs
  • Setting the build name and build number
  • Using multiple JFrog Platform instances
  • Publishing and accessing the build-info
• Using HTTP/s proxy
• Jenkins Configuration as Code
• Examples
• Contributions

Overview

The Jenkins JFrog Plugin allows for easy integration between Jenkins and the JFrog Platform. This integration allows your build jobs to deploy artifacts and resolve dependencies to and from Artifactory, and then have them linked to the build job that created them. It also allows you to scan your artifacts and builds with JFrog Xray and distribute your software package to remote locations using JFrog Distribution. This is all achieved by the plugin by wrapping JFrog CLI. Any JFrog CLI command can be executed from within your Jenkins Pipeline job using the JFrog Plugin.

Installing and configuring the plugin

1. Install the JFrog Plugin by going to Manage Jenkins | Manage Plugins.
   
2. Configure your JFrog Platform details by going to Manage Jenkins | Configure System.
   
3. Configure JFrog CLI as a tool in Jenkins as described in the Configuring JFrog CLI as a tool section.

Configuring JFrog CLI as a tool

General

To use JFrog CLI in your pipelines jobs, you should configure it as a tool in Jenkins by going to Manage Jenkins | Global Tool Configuration. You can use one of the following installation options:

Automatic installation from release.jfrog.io

If your agent has access to the internet, you can set the installer to automatically download JFrog CLI from https://releases.jfrog.io as shown in the below screenshot.

Automatic installation from Artifactory

If your agent cannot access the internet, you can set the installer to automatically download JFrog CLI from the JFrog instance you configured in Manage Jenkins | Configure System as shown in the below screenshot. To set this up, follow these steps:

1. Create a generic remote repository in Artifactory for downloading JFrog CLI. You can name the repository jfrog-cli-remote. This is the name we'll be using here, but you can also choose a different name for the repository.

   • In the Basic tab, set the repository URL to https://releases.jfrog.io/artifactory/jfrog-cli/
   • In the Advanced tab, uncheck the Store Artifacts Locally option.

2. In Manage Jenkins | Global Tool Configuration select the Install from Artifactory option as shown in the screenshot below.
   

3. Set the Server ID of your JFrog instanced, which you configured in Manage Jenkins | Configure System. Also set jfrog-cli-remote as the name of the remote repository you created to download JFrog CLI from. If you used a different name for repository, set this name here.
   

Manual installation

Install JFrog CLI manually on your build agent, and then set the path to the directory which includes the jf executable, as shown in the below screenshot.

Using JFrog CLI in your pipeline jobs

To have your pipeline jobs run JFrog CLI commands, add the following to your pipeline script.

Step 1: Define JFrog CLI as a tool, by using the tool name you configured. For example, if you named the tool jfrog-cli, add the following to the script:

tools {
    jfrog 'jfrog-cli'
}

Step 2: Use the jf step to execute any JFrog CLI command as follows:

// Upload all files in the target directory to the my-repo Artifactory repository.
jf 'rt u target/ my-repo/'

IMPORTANT: Notice the single quotes wrapping the command right after the jf step definition.

If the JFrog CLI command has arguments with white-spaces, you can provide the arguments as a list as follows:

jf(['mvn', 'clean', 'install', '-Ddeploy.testProperty=Property with space'])

When the above list syntax is used, the quotes required for the string syntax are replaced with quotes wrapping each item in the list as shown above. The above step is equivalent to the following shell command:

The list syntax also helps avoiding space and escaping problems, when some of those arguments use script variables.

Setting the build name and the build number

The plugin automatically sets the following environment variables: _JFROG_CLI_BUILDNAME and _JFROG_CLI_BUILDNUMBER with Jenkins's job name and build number respectively. You therefore don't need to specify the build name and build number on any of the build related JFrog CLI commands. If you wish to change the default values, add the following code to your pipeline script:

environment {
    JFROG_CLI_BUILD_NAME = "my-build-name"
    JFROG_CLI_BUILD_NUMBER = "18"
}

Using multiple JFrog Platform instances

If you have multiple JFrog Platform instances configured, you can use the –-server-id command option with the server ID you configured for the instance. For example:

jf 'rt u test-file my-repo –-server-id server-1'
jf 'rt u test-file my-repo –-server-id server-2'

Publishing and accessing the build-info

Build-info is the metadata of a build. It includes all the details about the build broken down into segments that include version history, artifacts, project modules, dependencies, and everything that was required to create the build. In short, it is a snapshot of the components used to build your application, collected by the build agent. See below how you publish the build-info from your pipeline jobs. This section should be placed inside the job after the execution of the JFrog CLI commands used for the build.

stage('Publish build info') {
    steps {
        jf 'rt build-publish'
    }
}

When the job publishes the build-info to Artifactory, you can access it by clicking on the build-info icon, next to the job run.

Using HTTP/S proxy

If you're using a JFrog platform that's situated behind an HTTP/S proxy, you should set up your proxy configuration under Manage Jenkins > Manage Plugins > Advanced.

To exclude the JFrog platform from going through a configured proxy, provide your JFrog platform's host details in the No Proxy Host section. Notice that the JFrog CLI is typically downloaded from releases.jfrog.io. You may need to add that to your list as well.

Jenkins Configuration as Code

To configure this plugin on Jenkins Configuration as Code, add the following sections to the jenkins.yaml:

1. Configure connection details to the JFrog platform

   unclassified:
     jFrogPlatformBuilder:
       jfrogInstances:
         - serverId: "acme"
           url: "https://acme.jfrog.io"
           artifactoryUrl: "https://acme.jfrog.io/artifactory"
           distributionUrl: "https://acme.jfrog.io/distribution"
           xrayUrl: "https://acme.jfrog.io/xray"
           credentialsConfig:
             credentialsId: "acme-secret-recipe"

2. Add JFrog CLI tool using one of the following methods:

• Automatic installation from release.jfrog.io:

  tool:
    jfrog:
      installations:
      - name: "jfrog-cli"
        properties:
        - installSource:
            installers:
            - "releasesInstaller"

• Automatic installation from Artifactory:

  tool:
    jfrog:
      installations:
        - name: "jfrog-cli"
          properties:
            - installSource:
                installers:
                  - artifactoryInstaller:
                      repository: "jfrog-cli-remote"

• Manual installation:

  tool:
    jfrog:
      installations:
        - name: "jfrog-cli"
          home: "/path/to/jfrog/cli/dir/"

Examples

These examples demonstrate only a fraction of the capabilities of JFrog CLI. Please refer to the JFrog CLI documentation for additional information.

Contributions

We welcome pull requests from the community. To help us improve this project, please read our Contribution guide.