This is not a bug (and actually might be lead to unexpected behavior on a lot of instances). Set your environment variables elsewhere, e.g. within Jenkins in the global and node configuration pages.
On 21.05.2014, at 15:49, Sapientlife <bpmi...@gmail.com> wrote: > Hi, > > Jenkins daemon is not starting up correctly. > > Looking at /etc/init.d/jenkins, it calls "daemon" from "/etc/init.d/functions" > > The daemon function does this: > cgroup $nice runuser -s /bin/bash $user -c "$corelimit >/dev/null 2>&1 ; $*" > > If you look at the man page for "runuser": > > -, -l, --login > > make the shell a login shell, uses runuser-l PAM file instead of default > one, clears all envvars except for TERM, initializes HOME, SHELL, > > USER, LOGNAME and PATH > > Note that daemon does not add -login to the command. > > Without the -l runuser is not reading the .bash_profile of the jenkins user. > > Is there a fix for this because it is causing Jenkins to not launch builds > with the correct environment variables. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
