|
||||||||
|
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/groups/opt_out.
Sorry for being so thick-headed.. I only now understood what the problem is and verified it myself. Set up a new Jenkins (1.502), set up a job that runs "env" and build it. Then go to the global configuration, click Save. Then build the job again. Compare the output from env command:
The environment variables BUILD_URL, JOB_URL, JENKINS_URL and HUDSON_URL are missing from the first run and only appear after you have visited global configuration AND clicked the Save button. It is not enough to visit the global configuration. You have to click the Save button.
This really is a bug. Not a huge bug and there is a good workaround. I'm not sure if anyone would set up a real Jenkins instance without even once visiting the global configuration... but it is a bug anyway.