![]() |
|
|
|
|
Change By:
|
Craig Ringer
(18/Jul/14 2:58 AM)
|
|
Description:
|
It looks like init-scripts don't get the environment variables defined for a node, or global environment variables defined in the main Configure Jenkins page, injected. At least for EC2 nodes.
The environment variables are present when running jobs, but not when running init scripts. Even when those environment variables are shown in the "Enviroment Variables" list under "System Information" for a node, an init script that has a line like:
{code}
env > /tmp/init-environ
{code}
will print an environment that doesn't include them, and shell substitutions won't use them.
In case they were set but not exported I tested with:
{code}
set > /tmp/set-environ
{code}
but the vars weren't present there either.
This makes it harder to parameterize init scripts.
The environment that was set was:
{code}
SHELL=/bin/bash
TERM=dumb
USER=root
SUDO_USER=root
SUDO_UID=0
USERNAME=root
MAIL=/var/mail/root
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
PWD=/home/admin
DEBIAN_PRIORITY=critical
SHLVL=1
SUDO_COMMAND=/bin/bash
HOME=/root
LOGNAME=root
DEBIAN_FRONTEND=noninteractive
SUDO_GID=0
_=/usr/bin/env
{code}
|
|
|
|
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/d/optout.
