|
||||||||||||||
|
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.
Not sure if it is the same bug or a new one:
When you have a build parameter, and you try to inject a value to it, the value is not injected.
Ways to reproduce:
JOB #1
----------
1. Add build parameter called BRANCH (or whatever name you like)
2. Add shell script with echo "BRANCH=test" > build.prop
3. Inject build.prop using the envinject plugin
4. echo ${BRANCH}
>> this echos blank value (or the default value set to parameter) instead of "test"
JOB #2
-----------
1. remove the parameter named BRANCH.
Rest of the steps (2-4) remain the same:
2. Add shell script with echo "BRANCH=test" > build.prop
3. Inject build.prop using the envinject plugin
4. echo ${BRANCH}
>> this echos "test"
We've upgraded Jenkins to 1.584 and envinject plugin to 1.90 and this behavior happens.
Job #1 and Job #2 should both echo "test" to the screen.
This was working before the upgrade we did (I don't remember which plugin version we had previously).
Thanks.