|
||||||||
|
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.
'env' is the environment for the build flow job itself, not the job(s) the build flow runs. There should be something here, but I'm not sure why it would be empty. In any case, I don't see how it would be useful at all. :/
It was pretty vague:
AbstractBuilds have their own interface, which you can find on the javadoc at http://javadoc.jenkins-ci.org/. One of these functions is getEnvironment, which can simply be referenced as "b.environment", because groovy automatically calls getters if a member field isn't accessible. getEnvironment returns a Map object.
Putting it all together gives you 'b.environment.get("P4_CHANGELIST")'.