-
Bug
-
Resolution: Unresolved
-
Minor
-
git-client 1.16.1
Jenkins 1.580.2
when setting a jenkins job that tracks 2 sources - */develop as jenkins trigger and ${branch} as a parameterized branch
the build always builds the develop branch(as if it was externally triggered) and ignores the ${branch} parameter.
without this option users are forced to create 2+ build jobs doing the same thing, therefor have double the maintenance and bugs because of code duplication
attached the Stash screen that sets up the jenkins trigger
I don't understand how to duplicate the bug you're reporting. Can you provide a series of steps which will show the bug?
Steps I tried while attempting to duplicate the bug:
Is the problem that the parameter is ignored when a non-parameterized branch name is also to be monitored?