|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I'm not sure if I understand you, but If I'm right it is maybe a documentation problem. From what I understand in your report, you are actually creating a project from a template, and in that case, the only action taken when copying the template is to replace the repository url and enable the project because template could be disabled). It seems that you are expecting that some variables defined on the template get replaced with some values from payload.
It looks like REPOSITORY_URL is actually replaced, but it isn't. Whatever the template has configured as git url is discarded and filled from payload (actually, I use templates with empty git url). And accordingly, the branch specification is kept exactly as in template. And your final job has one useless parameter (probably two).
If you remove the two parameters of your template and set the branch specifier to origin/master, you'll probably get what you expect. But take into account that templating only acts when the push is for an unknown repo. Once you get the template realized, you need to enable "classic" automatic branch creation to get extra instances for that same project when other branches are pushed.