-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
Triggering a build by SCM change works fine with load rules + branches + label,
but Jenkins detects changes only for well-known labels (MY_LABEL_1).
But sometimes it would be very helpful to have wildcards available for labels,
e.g. if you know the "basename" of a new label, but not its revision (MY_LABEL_*).
Example: I want to trigger a build only if there's a new element version
available in main branch tagged with a label: <load rule>@@/<branch>/MY_LABEL_*
How about if the labels were parsed from config spec? For us it would work perfectly, if all the labels in config spec were taken into account. That is, applying or removing any label included in config spec would trigger a build. In this case, listing the labels separately in job configuration would be redundant.