Method such as a tickbox to change the behavior of 'Include Filter' against multibranch definition to become an exclude filter.
Example Usage Case
Project includes the following branches and want to exclude *-Private from multi-branch definition:
1.2.3-Rel
1.2.3-QA
1.2.3-Dev
1.2.3-Private
1.2.4-Rel
1.2.4-QA
1.2.4-Dev
1.2.4-Private
Workarounds at the moment would be:
- Use Perforce protections to hide *-Private from Jenkins user.
- Have multiple inclussionary expressions. For example '(.[1-9].*Rel)|(.[1-9].QA)|(.[1-9].*Dev)
- is duplicated by
-
JENKINS-63625 Multibranch pipeline cannot exclude/remove perforce streams
- Closed