|
||||||||
|
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.
Build parameters are the most obvious source. Others are the characteristic environment variables defined for every build (such as BUILD_NUMBER, BUILD_ID, JOB_NAME, ...), environment variables defined globally or on nodes, plugins such as Mask Passwords or Env-Inject enabled for your project, SCMs may provide them (like SVN_URL from Subversion plugin), the install location of the JDK configured for your project, ...
But setting a value in a shell build step and using it afterwards in the rest of the job configuration has to the best of my knowledge never worked. Some references:
https://groups.google.com/d/msg/jenkinsci-users/XW3-n7DFVI8/IqpMpsKYlkAJ
https://groups.google.com/d/msg/jenkinsci-dev/aAYJL2vFsx8/YVo1Xdp3UjEJ
https://groups.google.com/d/msg/jenkinsci-users/XPt8jbmj8CI/ZS4RMbip6o0J
None of them state it outright, but if it were this easy, you'd think one person would speak up and mention this. People are even writing plugins to provide this feature.