Support for pipeline name different than branch path

[dcoraboeuf]

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.

Objective: find a way to enable this separation, by allowing the project to enter an additional parameter when generating a branch:

• the SEED_BRANCH and the BRANCH will keep their meaning - that would be in this case the branch "name"
• the new parameter, BRANCH_SCM, is propagated to the branch seed for being used by the pipeline generator

[dcoraboeuf]

• [x] Update Wiki documentation

[dcoraboeuf]

Make the BRANCH_SCM parameter available to the pipeline generator