-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: NXP-10.x
-
Fix Version/s: NXP-10.x
-
Component/s: Continuous Integration
-
Sprint:DevTools-06
Looking at the swarm-priv-1 slave, the environment exposed to Jenkins is not the same as the one a user inherits by SSH. This inconsistency is too much error prone.
https://qa.nuxeo.org/jenkins/computer/swarm-priv-1/script println System.getenv().size() 45 $ docker -H tcp://swarm-qa.nuxeo.org:4000 exec -it -u jenkins qa-ovh02.nuxeo.com/swarm-priv-1 wc -l /etc/environment 20 /etc/environment $ docker -H tcp://swarm-qa.nuxeo.org:4000 exec -it -u jenkins qa-ovh02.nuxeo.com/swarm-priv-1 env|wc -l 13 --- https://qa.nuxeo.org/jenkins/computer/priv-01-1/script println System.getenv().size() 32 $ docker -H tcp://swarm-qa.nuxeo.org:4000 exec -it -u jenkins qa-ovh01/priv-01-1 env|wc -l 10
A Docker slave environment should mostly not differ, regardless how it is launched or connected to.
This inconsistency was remarked while tracking the GEM_HOME property to understand why fastlane is no more found on the slaves:
$ docker -H tcp://swarm-qa.nuxeo.org:4000 exec -it -u jenkins swarm-pub-910-0 fastlane --version (...) fastlane 2.112.0 $ docker -H tcp://swarm-qa.nuxeo.org:4000 exec -it -u jenkins qa-ovh01/swarm-pub-0 fastlane --version OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "exec: \"fastlane\": executable file not found in $PATH": unknown
