-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Hudson 1.344, Hudson batch task plugin 1.12
Some last Hudson version brought a new "Set environment variables" field in job configuration.
This environment variables not inherited or parsed by shell tasks.
One has to duplicate the needed variables in order to be used in task's script commands.
Although the job's environment variables are passed, I've only tested these: parameter variables, $WORKSPACE, $JAVA_HOME, $CLEARCASE_VIEWNAME, etc. Global Environment variables set in hudson's configuration are also correctly parsed.
I don't know if this an issue with tasks or because the "Set environment variables" field is coming after tasks definition in job's configuration view.
Thanks in advance.
–
UPDATED!
[JENKINS-5580] Environment variables from setenv plugin are not inherited/parsed by batch tasks
hmonteiro
created issue -
Description updated.
I don't know if I mistakenly mixed description/report of tickets or something when checking and creating this and other tickets.
I've writen the description in a way that reports a reverse behaviour that I was noticing and wanted to report here. Description is now corrected.
hmonteiro
added a comment - - edited Description updated.
I don't know if I mistakenly mixed description/report of tickets or something when checking and creating this and other tickets.
I've writen the description in a way that reports a reverse behaviour that I was noticing and wanted to report here. Description is now corrected.
hmonteiro
made changes -
| Description |
Original:
Hudson build's environment environment variables are not inherited or parsed by shell. One has to duplicate the needed variables in order to be used in task's script commands. I presume none of the job's environment variables are passed, but I've only tested these: parameter variables, $WORKSPACE, $JAVA_HOME, $CLEARCASE_VIEWNAME. Also, build's new 'Set environment variables' field is also not inherited by tasks. As well as Hudson's global environment variables that can be configured in Hudson's Configuration panel. Thanks in advance. |
New:
Some last Hudson version brought a new "Set environment variables" field in job configuration. This environment variables not inherited or parsed by shell tasks. One has to duplicate the needed variables in order to be used in task's script commands. Although the job's environment variables are passed, I've only tested these: parameter variables, $WORKSPACE, $JAVA_HOME, $CLEARCASE_VIEWNAME, etc. Global Environment variables set in hudson's configuration are also correctly parsed. I don't know if this an issue with tasks or because the "Set environment variables" field is coming after tasks definition in job's configuration view. Thanks in advance. -- UPDATED! |
hmonteiro
added a comment - Just a small correction,
"Set environment variables" field comes from a plugin called "Setenv" and not from Hudson. The plugin is not listed in the selectable "Component/s" field when opening tickets (that's why I mentioned new hudson's field), although I just found it listed as a plugin in plugins wiki page.
The "Set environment variables" field appears immediately before build steps. I've also opened a ticket regarding this plugin's behaviour, that is, not exporting variables all over job's configuration and only to the execution sections.
Thanks.
hmonteiro
added a comment - Just a small correction,
"Set environment variables" field comes from a plugin called "Setenv" and not from Hudson. The plugin is not listed in the selectable "Component/s" field when opening tickets (that's why I mentioned new hudson's field), although I just found it listed as a plugin in plugins wiki page.
The "Set environment variables" field appears immediately before build steps. I've also opened a ticket regarding this plugin's behaviour, that is, not exporting variables all over job's configuration and only to the execution sections.
Thanks. | Summary | Original: Environment variables are not inherited/parsed by tasks | New: Environment variables from setenv plugin are not inherited/parsed by batch tasks |
| Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] | New: Alan Harder [ mindless ] |
Code changed in hudson
User: : mindless
Path:
trunk/hudson/plugins/batch-task/pom.xml
trunk/hudson/plugins/batch-task/src/main/java/hudson/plugins/batch_task/BatchRun.java
http://jenkins-ci.org/commit/27256
Log:
[batch-task] [FIXED JENKINS-5580] Not sure if tasks should use all BuildWrappers
(xvnc for example), but look specifically for wrapper from setenv plugin and
apply its env settings.
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
hmonteiro
added a comment - Hi there,
Funny that you mentioned xvnc plugin, we also use it to build packages and exporting it's variable to tasks would also be great.
But like you, I'm also not sure if using all BuildWrappers should interfere or mess with something else that we can't see now. I mean, I only use a specific set of plugins, and could be that some can give strange behaviours because of what you mention.
Either way, thanks for this fix.
hmonteiro
added a comment - Hi there,
Funny that you mentioned xvnc plugin, we also use it to build packages and exporting it's variable to tasks would also be great.
But like you, I'm also not sure if using all BuildWrappers should interfere or mess with something else that we can't see now. I mean, I only use a specific set of plugins, and could be that some can give strange behaviours because of what you mention.
Either way, thanks for this fix.
I made a task with "env" to print env vars.. I see build vars (WORKSPACE and JAVA_HOME) and global vars (from main /configure page) here. I don't see any problem since batch task 1.11 which includes
JENKINS-5039fix.