Managing Pipeline Sources

JFrog Pipelines Documentation

JFrog Pipelines
Content Type
User Guide

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 add, view, edit and sync pipeline sources. Non-administrator users can only view and sync pipeline sources.


To successfully add a pipeline source, ensure the following:

  • The credentials used in the source control integration should have admin access to the specified source control repository. Admin privileges are used to add a webhook that allows Pipelines to be notified of changes in the repository.

  • Pipelines 1.26.0 and lower: The repository path is valid. To know the exact path to specify, inspect the git clone URL of that repository in your source control system and copy the value.

    Here are some examples:

    • GitHub / GitHub Enterprise: - use myuser/basic-pipeline

    • Bitbucket Server (Private repository): - use project-id/repo-name

    • Bitbucket Server (Individual repository): - use ~myuser/myfirstrepo

    • Bitbucket: - use teamspace/test-repo

    • GitLab: - use user1/repo1

  • Branch name is valid and the credential used in the Git integration for the pipeline source has access to the branch.

  • Add an integration for the source control system where your pipeline file repository is (or will be) located. The integration can be one of these source control system providers: