Creating Multibranch Pipelines

JFrog Pipelines Documentation

ft:sourceType
Paligo

A multibranch pipeline enables development teams to maintain discrete pipelines for different branches of the same project. The pipeline of each branch will have its own run history and logs.

Many development organizations use a branching model (such as GitFlow) for collaboration on large projects. In this style of workflow, development teams maintain a main source code branch while creating feature branches for each feature in-progress. The feature team will merge those changes into the main branch when feature development is complete, and delete the feature branch.

In this agile development model, feature branches are created and destroyed frequently. Manually administering each branch as a new pipeline source can be a slow and annoying chore.

When you designate a pipeline source as multibranch, Pipelines automatically creates a new pipeline from each branch's pipeline config, and destroys the pipeline when the branch is destroyed. In this way, the main branch and included child branches will all have their own pipeline, each of which can be independently viewed, run, and triggered.

The following steps are involved in creating multi-branch pipelines:

#

Task

Description

For more information, see...

1

Configure a multibranch pipeline

Configure a source as multibranch, including or excluding branch patterns to determine what branched participate.

Configure a Multibranch Pipeline Source

2

Declare a multibranch pipeline

Use {{gitBranch}} in the GitRepo resource definition to define branches to include.

Declare a Multibranch Pipeline

3

Run the pipeline

Expand a multibranch pipeline source to view and run it.

Run Multibranch Pipelines