Branch SCM path

In some contexts, the SCM path to the branch might be different than the name to give to the branch pipeline and folder, and a simple naming convention cannot be enough.

In this non trivial case, we must also be able to change the branch pipeline to take into account a new SCM path.

This is typical case when a release or version is attached to a trunk or master, and that its semantic will change with time.

For example:

• a trunk starts to support 1.0 - we create a 1.0 pipeline to support the trunk
• upon branching for 1.0, we regenerate the 1.0 pipeline to use the new 1.0 branch and we generate a new 1.1 pipeline for the trunk

This kind of situation should be avoided but does exist in some projects where the branch = version paradigm has not been applied yet. In the later case, there is no need to operate a dichotomy between a branch name and a branch path - they are the same.

To enable this feature on a project, you can configure the project and enable the Extra Branch SCM parameter.

For a project which has this parameter set to Yes, an additional BRANCH_SCM parameter is available when generating or updating a branch from the project seed. This parameter is used in the branch seed to download the Seed configuration and is available for the branch pipeline script.

Note that the SEED_BRANCH and the BRANCH are still available and keep their meaning - that would be in this case the branch "name"

See also

• Generation
• Extensions