-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Ubuntu 12.04
I have a build parameter, branch, which is passed to the git "Branches to build" setting. When this parameter is set to '*', '**', or is empty, the last built revision gets built again instead of an updated branch HEAD. Setting this parameter to a specific branch name, such as 'development' or 'master' will build the HEAD of the specified branch. Directly setting git "Branches to build" to '*', '**', or leaving it empty will cause an updated branch HEAD to build properly.
- is duplicated by
-
JENKINS-21719 Unable to get Branch to build variable to work with wildcard
-
- Open
-
- is related to
-
JENKINS-23714 specified git branch to checkout/build is not used
-
- Closed
-
I was able to verify the bug as reported. A parameterized build with branch as the parameter does not correctly use the value of that parameter if the value contains a wildcard and ${branch} is inserted into the branch name field.
The exact same job definition runs successfully if the parameter value provides an exact name for an existing branch.
The key problem seems to be related to wildcard expansion in the parameter somehow.