On Mon, May 21, 2018 at 06:53:25PM +0200, Andrea Bolognani wrote:
Instead of having to specify this separately for every
guest due to minor differences in the environment, figure
it out at login time by asking Perl itself for the
information we need.
We still have the problem that any time a package update is done it
might pull in a newer Perl, which will change the path, but our
Jenkins slave never picks it up until the VM is rebooted.
I wonder if we can solve this by instead of putting all these
env vars in the main bash profile, we create a
'jenkins-ci.sh'
that contains all the env variables. We can then source that
from the bash profile, and also source it as the first thing
we do in every build job too.
Regards,
Daniel
--
|:
https://berrange.com -o-
https://www.flickr.com/photos/dberrange :|
|:
https://libvirt.org -o-
https://fstop138.berrange.com :|
|:
https://entangle-photo.org -o-
https://www.instagram.com/dberrange :|