Also important. I use phing. Which means that sourcing a file won't help,
since that is done in an Exectask, which is isolated from the other tasks.
I can't source a file first and then run another task expecting the env
variables to be manipulated.
On Monday, 4 May 2015 09:59:39 UTC+2, Dieter Blomme wrote:
>
> Hi,
>
> I need to run jobs where the PATH is set by the server itself (e.g. by
> .bashrc), so it can be manipulated by chef/puppet/... At this point, I
> can't figure out how to do this, since jenkins runs the shell scripts
> inside a job as non-interactive, non-login shells. Part of the jobs are
> running bundle install and bundle exec compass compile, which requires the
> PATH to be set properly. What is the best way to do this, keeping in mind
> server install and manipulation is through provisioning tools (no manual
> steps)?
> I have researched the BASH_ENV, it doesn't seem usable.
> I have tried using a /etc/profile.d/path.sh file and sourcing /etc/profile
> as a first step in the build process, that works, but seems to be very
> funky.
>
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/ad95b404-ee0c-4cfd-acda-b0312e24d211%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
