|
||||||||
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-14097) Allow Script Path/Content to add/override environment variables for the build job
dave.ehrenber...@solipsys.com (JIRA) Mon, 18 Jun 2012 04:34:23 -0700
- [JIRA] (JENKINS-14097) Allow Script P... dave.ehrenber...@solipsys.com (JIRA)
- [JIRA] (JENKINS-14097) Allow Scr... dave.ehrenber...@solipsys.com (JIRA)
- [JIRA] (JENKINS-14097) Allow Scr... dave.ehrenber...@solipsys.com (JIRA)
- [JIRA] (JENKINS-14097) Allow Scr... dave.ehrenber...@solipsys.com (JIRA)
- [JIRA] (JENKINS-14097) Allow Scr... dave.ehrenber...@solipsys.com (JIRA)
- [JIRA] (JENKINS-14097) Allow Scr... dave.ehrenber...@solipsys.com (JIRA)
So you are saying there is no "one" job environment currently available in Jenkins? Do you know the existing Jenkins JIRA issue?
If there were "one" environment, then your plugin change would work since a sub-shell environment can add to/modify existing environment variables from the main shell via the export (in bash) or setenv (in tcsh).