Managing Pipeline Sources

JFrog Pipelines Documentation


A Pipeline Source represents a source control repository (such as GitHub or BitBucket) where Pipelines definition files can be found. A pipeline source connects to the repository through an integration. After a pipeline source is added, Pipelines automatically loads all config files from the repository that matches the specified filename filter.


Administrator users can create, view, edit and sync pipeline sources. Non-administrator users can only view and sync pipeline sources.

Administering Pipeline Sources

Only users with administrator privileges can manage pipeline sources.Introduction to Users and Groups


To successfully add a pipeline source, ensure the following:

Adding a Pipeline Source (1.31.0 and higher)

To add a source control repository as a Pipeline Source:

  1. Go to Administration | Pipelines | Pipeline Sources.

  2. In the resulting Pipeline Sources display, click Add Pipelines Source and click From YAML.

  3. In the Add YAML Pipeline Source page, click one of the following:

    • Single Branch

    • Multi Branch

  4. Click to select the protocol type to be used for cloning the repository when the pipeline source is synced:

    • SSH

    • HTTPS

  5. Complete the Single/Multi Branch form:




    Enter a unique name for the pipeline source.

    SCM Provider Integration

    Click the SCM Provider Integration field and select your source control integration from the dropdown list. Only integrations that are compatible for use as a Pipeline Source will be included in the dropdown list.

    Repository Full Name

    Based on the information you have provided for the selected integration, such as API token, all the relevant repositories are listed in the Repository Full Name field. Select the path of the repository where your pipeline files are stored. If the name of the repository is not auto-fetched, enter the full name of the repository where your pipeline files are stored.

    Branch (Single Branch only)

    Based on the SCM provider and Repository Full Name you have provided, all the available branches are automatically fetched (for example, main). Select the required branch. If the name of the branch is not auto-fetched, enter the name of the branch.

    Exclude (Multi Branch only)

    Specify the Exclude Branch Patternas a regular expression for the matching branch names to exclude.

    Include (Multi Branch only)

    Specify the Include Branch Pattern as a regular expression for the matching branch names to include.

    Sync all branches toggle

    (Multi Branch only)

    When a new multi branch pipeline source is added, only the default branched is synced. To sync all the branches based on the Exclude/Include pattern, click the Sync all branches toggle. If Exclude/Include pattern is not provided, all branches are synced.

    In addition, when a new commit is pushed to thematching branch, that particular branch is synced.

    Folder Name

    Provide the name of the directory where the YAML config is available.

    • To use Folder Name, in the SCM repository, place your YAML files in a directory named .jfrog-pipelines. This directory can be the root or one level below the root. Directories beyond this level are not supported.

    • Following are the possible directory structures for monorepos:

      - root

      ------ .jfrog-pipelines


      - root

      ---- .jfrog-pipelines

      -------- service1

      -------- service2


      - root

      ---- service1

      --------- .jfrog-pipelines

      ---- service2

      --------- .jfrog-pipelines

    • The .jfrog-pipelinesdirectory can contain any number of YAML files.

    • To parse all YAML files in the root directory, enter ".". However, other pipeline sources cannot point to this repository.

    • You can create multiple pipeline sources pointing to the same SCM repository as long as the directory names are different (and none of them point to root).

    Recommended Directory Structure for using Folder Name

    Here are some examples of the supported directory structure:

    YAML Files Location

    Folder Name Path

    YAML files are in the .jfrog-pipelines root directory

    Enter . (dot) or .jfrog-pipelines in theFolder Name field to fetch all the YAML files

    YAML files are in the .jfrog-pipelines/project1 directory

    Enter.jfrog-pipelines/project1 in the Folder Name field to fetch the YAML files in the .jfrog-pipelines/project1 directory

    YAML files are in the following directories:

    • .jfrog-pipelines

    • .jfrog-pipelines/project1

    • .jfrog-pipelines/project2

    Enter . (dot) or .jfrog-pipelines in the Folder Name field to fetch all the YAML files in all directories


    Enter .jfrog-pipelines/project1 in the Folder Name field to fetch the YAML files in the .jfrog-pipelines/project1 directory

    Enter .jfrog-pipelines/project2 in the Folder Name field to fetch the YAML files in the .jfrog-pipelines/project2 directory

    YAML files are in the following directories:

    • .jfrog-pipelines

    • service1/.jfrog-pipelines

    • service2/.jfrog-pipelines

    Enter . (dot) or .jfrog-pipelines in the Folder Name field to fetch the YAML files in the .jfrog-pipelines directory, but YAML files in the service1 /.jfrog-pipelines and service2 /.jfrog-pipelines directories will not be included.


    Enter service1 /.jfrog-pipelines in the Folder Name field to fetch specific YAML files in the service1 /.jfrog-pipelines directory

    Enter service2 /.jfrog-pipelines in the Folder Name field to fetch specific YAML files in the service2 /.jfrog-pipelines directory

    If you have a monorepo with multiple services within a single repo, a directory structure such as the following is recommended:

    Existing Directory Structure

    Recommended Directory Structure











    Local Artifactory Token Permissions

    When a pipeline source is added to a custom Project, all pipelines associated with this pipeline source will have access to a local Artifactory integration by default. This integration enables you to connect to your local Artifactory instance to push artifacts, without having to explicitly create an Artifactory integration. However, unlike the custom Artifactory integration, which can be used to connect to any Artifactory instance, the local Artifactory integration can only connect to your local Artifactory instance. In addition, while the custom Artifactory integration uses API key for authentication and permissions, the local Artifactory integration uses scoped token.


    Local Artifactory integration has the following limitations:

    • It can only be used in custom Projects. The default Project does not support this integration.

    • It can only be used with repositories created within custom Projects.

    • It can only be used in Bash steps.


    Read permission is enabled by default for all local Artifactory integrations. When required, you can add the following additional permissions for your pipeline source. All pipelines associated with that pipeline source will then use these permissions:

    • Read: Download artifacts (available by default)

    • Write: Upload or update artifacts

    • Delete: Delete artifacts

    • Manage: Change the permission settings for other users

    Usage in Pipelines YAML

    The local Artifactory integration can be added as an input to any Bash step. To do this, use {{ .jfrog-pipelines.localArtifactory }} as a placeholder for the integration. It can be used at both pipeline-level and step-level.

    When you add this integration directly to a Bash step, the JFROG_LOCAL_ARTIFACTORY_TOKEN environment variable is automatically made available to be used at runtime. This environment variable creates a scoped token with read permissions. When the pipeline YAML is added as a pipeline source, the permissions for the token can be elevated to Write, Delete, and/or Manage. If the pipeline source includes more than one pipeline, the new permissions will be applicable for all the pipelines in the source.

      - name: myRepo_native
        type: GitRepo
          path: jfrog/jfrog_pipelines
          gitProvider: myGithub
            include: master
      - name: myPipeline_native
          - name: first_step
            type: Bash
                - name: {{.jfrog-pipelines.localArtifactory}}
                - echo "first_step"
                - jfrog config add jftest-$step_id --url --access-token ${JFROG_LOCAL_ARTIFACTORY_TOKEN}
                - touch test.txt
                - echo "hello" > test.txt
                - jfrog rt upload test.txt demo-sampleRepo/test.txt --server-id jftest-$step_id
          - name: second_step
            type: Bash   
                - name: first_step
                - echo "second_step"
                - echo "$JFROG_LOCAL_ARTIFACTORY_TOKEN"
Validating YAML

Before adding a pipeline source, you have the option of validating your pipelines, resources, and values YAMLs and then committing it to the SCM. This enables you to get instant feedback on pipeline sync errors. The YAML validator will validate your YAML for both semantic and syntactic errors.

To validate your YAML:

  1. Click Validate YAML.

  2. Either enter the YAML and paste the YAML contents in the Pipelines YAML and Resources YAML fields. If you have a values YAML, enter the YAML contents in the Values YAML field. For more information about the Pipelines DSL, see Defining a Pipeline.

    As the YAML content is entered, it is validated and syntactic errors, if any, are displayed.

  3. After fixing all the syntactic errors, click Validate to validate the YAML for semantic errors.

Viewing Pipeline Sources

To view the list of pipeline sources already added to Pipelines, go to Administration | Pipelines | Pipeline Sources or Application | Pipelines | Pipeline Sources.

The page displays the list of pipelines sources that are available to you according to the permission targets defined in the JFrog Platform. Your user account must be granted permissionsfor a pipeline source for it to be shown.Introduction to Permissions

Each row of the pipeline sources list includes the following:




  • For new pipeline sources: This is the name you provided while creating the pipeline source

  • For existing pipeline sources: This defaults to repositoryName/branch for single branch and repositoryName for multi-branch

Git Repository

The source repository path of the pipeline source


The Project that the pipeline source belongs to

Latest Status

The success/failure status of the last sync

Config File Filter

The filter string for the pipeline config files

Last Sync

The time and date of the last sync

Changed By

Name of the user who made the last update to the pipeline source


The commit SHA that triggered the last sync


Click the Logs link to view the log from the last sync. Use this to diagnose a failure to sync a pipeline source.

If the pipeline source is a multi branch source, the row presents aggregate information for all branches, and can be expanded/collapsed to show the sync status of each branch.

Syncing a Pipeline Source

When any of the pipeline config files have changed, you will need to sync the pipeline source to reload:

  1. Go to Administration | Pipelines | Pipeline Sources and click the Actions button located at the far right.

  2. Click Sync.