Only users with administrator privileges can manage pipeline sources.
To successfully add a pipeline source, ensure the following:
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:
To add a source control repository as a Pipeline Source:
main
). Select the required branch. If the name of the branch is not auto-fetched, enter the name of the branch.pipelines.resources.yml
and your pipelines in pipelines.workflows.yml
, then you might enter pipelines.*.yml
.If you have multiple yaml config files, then enter .*yml
.
pipelines.yml
, if you are using a values.yml
, ensure both files are added to the filter, using (pipelines|values).yml
.Click the Select Template Version field and select the version for the template.
In the resulting Specify values file page, click one of the following from the Read YAML values from drop-down:
main
). Select the required branch. If the name of the branch is not auto-fetched, enter the name of the branch..values.yml
file, which contains the values for the template.If JFrog Pipelines successfully syncs with the repository, the Status field displays "Success". Otherwise, it displays "Failed".
All pipeline config files committed to the repository will be automatically loaded into JFrog Pipelines, and all defined pipelines from that source are listed in the pipeline list.
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 permissions for a pipeline source for it to be shown.
Each row of the pipeline sources list includes the following:
Name |
|
Git Repository | The source repository path of the pipeline source |
Project | 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 |
Context | The commit SHA that triggered the last sync |
Logs | 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.
When any of the pipeline config files have changed, you will need to sync the pipeline source to reload:
To view the logs of all synchronized config files:
Pipelines provides an option to enable auto-sync for pipelines sources that are out of sync. For more information, see Pipeline Source Sync Recovery. |
When a pipeline source is deleted, it deletes all the pipelines associated with the source.
To delete a pipeline source:
A pipeline source cannot be deleted if any of its associated pipeline is still running. You can either cancel the run or wait for the run to complete and then delete the pipeline source. |
When one or more branches are created for a Multibranch pipeline source, the webhooks may not be processed correctly, resulting in those branches not being added to the pipeline source.
Pipelines can automatically fetch and sync missing branches in a multibranch pipeline source based on the selected SCM integration and the full name of the repository.
To do this: