Use triggering branch as source branch in git-sourced CI jobs
Currently:
We have to define a single fixed source branch in a CI job, when it has a Git-Source.
Desired:
Option to say "use triggering branch". It should use the branch, where current commit-hook-call comes from.
It should allow Pipelines to test also all development branches e.g. with "Validation only" CI-job.
11
votes
-
David Westberry
commented
Very needed, but also the ability to filter which branches execute the job. I should be able to say "use triggering branch" but also "filter branch names" using a pattern, like release/*
-
Nikita Belov
commented
Very needed
-
Marco Pinder
commented
This would really help when following the Gitflow Workflow model that makes use of temporary 'release' branches in a Git source.