|
||||||||
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 |
- [JIRA] (JENKINS-14623) EnvInject ignore... ra...@java.net (JIRA)
- [JIRA] (JENKINS-14623) EnvInject i... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-14623) EnvInject i... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-14623) EnvInject i... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-14623) EnvInject i... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-14623) EnvInject i... ra...@java.net (JIRA)
I eventually did, but I find this behavior unfriendly and not intuitive. In this particular situation I could not restart Jenkins at once, since there were other jobs building, some of them run for many hours. So in case I could not restart Jenkins instance, I also could not build another job which relied on global configuration. Built-in variable setting does not work that way and does not require Jenkins restart after changing global configuration.