|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
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.