Hi Daniel, The problem I having though with this behavior is that when a build is started from the Jenkins GUI the shell that the build runs in does not get access to our SCM AccuRev no matter where we edit the environment variables .bashrc/.bash_profile, /etc/profile, /etc/sysconfig/jenkins ...
On Wednesday, May 21, 2014 9:49:38 AM UTC-4, Sapientlife 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
