GitLab Templates for JFrog

This repository includes pipeline templates for GitLab CI, for a quick and easy integration with the JFrog Platform.

The templates use the .setup-jfrog.yml pipeline scripts. The script is included by each of the templates, and sets up the integration between the pipeline and the JFrog Platform.

The script does the following:

  • Installs JFrog CLI

  • Configures JFrog CLI to work with the JFrog Platform

  • Sets the build name and build number values with the values of $CI_PROJECT_PATH_SLUG-$CI_COMMIT_REF_NAME and $CI_PIPELINE_ID respectively, to allow publishing build-info to Artifactory

  • Optionally replaces the default Docker Registry with an Artifactory Docker Registry


  1. Ensure you have the connection details for the JFrog Platform.

  2. Store the JFrog Platform connection details on GitLab

  3. Optionally set the URL of your Artifactory Docker Registry as the value of the JF_DOCKER_REGISTRY variable

  4. Add the setup-jfrog pipeline script in your GitLab pipeline

Storing the JFrog Platform Connection Details

Store the connection details of your JFrog Platform as GitLab CI/CD variables by using one of the following variables combinations:

  1. JF_URL - Anonymous access (no authentication)

  2. JF_URL + JF_USER + JF_PASSWORD - Basic authentication

  3. JF_URL + JF_ACCESS_TOKEN - Authentication with JFrog Access Token. NOTE: When pulling and pushing docker images from/to Artifactory, the JF_USER variable is also required, in addition to the JF_ACCESS_TOKEN variables

Adding the setup-jfrog Script in Your Pipeline

Including the Script

The templates included in this repository already have the setup-jfrog script included as follows:

  - remote: ''

For Windows agents, use:

  - remote: ''

You also have the option of downloading the matching script from, adding it to your project, and including it in your pipeline as follows:

  - local: '.setup-jfrog-unix.yml'

You can also include it from one of your projects as follows:

  - project: 'my-group/my-project'
    file: '/script/.setup-jfrog-unix.yml'

Referencing the Script

Once the script is included in your pipeline, you'll need to reference it from any script or before_script sections in the pipeline as shown below:

    - !reference [.setup_jfrog, script]

At the end of your script, or as part of after_script, you should add the cleanup reference:

    - !reference [.cleanup_jfrog, script]

Downloading the setup-jfrog script and JFrog CLI from Artifactory

If your GitLab environment is air-gapped, you would want your pipeline to avoid downloading the setup-jfrog script and also JFrog CLI from Here's how you do this:

As shown in the above Including the Script and Referencing the Script sections, you have the option of copying the setup-jfrog script into your pipeline, and thus avoiding its download. Since the setup-jfrog script downloads JFrog CLI from, you should also configure the script to download JFrog CLI from a remote repository in your JFrog Artifactory instance. Follow these steps to have JFrog CLI downloaded from your Artifactory instance:

  1. Create a remote generic repository in Artifactory pointing to

  2. Add the JF_RELEASES_REPO variable to GitLab with the name of the repository you created

Additional Optional Variables

Configurations can be done via Project Settings > CI/CD > Variables:



Docker registry in Artifactory. For more info, see Getting Started with Artifactory as a Docker Registry


JFrog project key to be used by commands which expect build name and build number. Determines the project of the published build.


Use a specific JFrog CLI version instead of the latest version. The minimal version allowed is: 2.17.0

See more environment variables in the JFrog CLI documentation.


  • For Linux / Mac: cURL


  1. If the JF_DOCKER_REGISTRY and JF_ACCESS_TOKEN variables are set, then the JF_USER variable is required.

  2. Build info collection is unavailable when:

    • Working with a docker registry without JFrog CLI.

    • Running separate jobs on temporary agents or docker containers.

Behind the Scenes

The setup-jfrog scripts are maintained in the jfrog-cli repository. Each yaml includes two hidden jobs with scripts named .setup_jfrog and .cleanup_jfrog, which can be referenced by the pipeline after the script is included.


Build and Upload to JFrog Artifactory

  • .NET

  • Go

  • Gradle

  • Maven

  • npm

  • NuGet

  • Pip

  • Pipenv

  • Yarn Berry

$ jf mvn clean install
18:26:42 [πŸ”΅Info] Running Mvn...
18:26:58 [πŸ”΅Info] These files were uploaded:

πŸ“¦ libs-snapshot-local
└── πŸ“ org
    └── πŸ“ jfrog
        └── πŸ“ test
            β”œβ”€β”€ πŸ“ multi2
            β”‚   └── πŸ“ 3.7-SNAPSHOT
            β”‚       β”œβ”€β”€ πŸ“„ multi2-3.7-20230227.162644-67.jar
            β”‚       └── πŸ“„ multi2-3.7-20230227.162644-67.pom
            β”œβ”€β”€ πŸ“ multi1
            β”‚   └── πŸ“ 3.7-SNAPSHOT
            β”‚       β”œβ”€β”€ πŸ“„ multi1-3.7-20230227.162644-69.pom
            β”‚       β”œβ”€β”€ πŸ“„ multi1-3.7-20230227.162644-69-tests.jar
            β”‚       β”œβ”€β”€ πŸ“„ multi1-3.7-20230227.162644-69-sources.jar
            β”‚       └── πŸ“„ multi1-3.7-20230227.162644-69.jar
            β”œβ”€β”€ πŸ“ multi
            β”‚   └── πŸ“ 3.7-SNAPSHOT
            β”‚       └── πŸ“„ multi-3.7-20230227.162644-67.pom
            └── πŸ“ multi3
                └── πŸ“ 3.7-SNAPSHOT
                    β”œβ”€β”€ πŸ“„ multi3-3.7-20230227.162644-67.pom
                    └── πŸ“„ multi3-3.7-20230227.162644-67.war

Security Audit with JFrog Xray

  • .NET

  • Go

  • Gradle

  • Maven

  • npm

  • NuGet

  • Pip

  • Pipenv

  • Yarn Berry

Last updated

Β© 2024 JFrog Ltd All Rights Reserved