-
Bug
-
Resolution: Incomplete
-
Minor
-
None
-
Jenkins 2.164.3 on Suse 12.1 using stand alone jenkins with slave also on suse 12.1.
when running a job some environment variables are not being taken.
In this example the environment is setup behind a proxy, and I need to make a connection to a server within the environment bypassing the proxy.
The job print out shows that the server is attempting to connect to the target server through proxy, so the job fails as it can't.
Viewing the Environment variables for that job I see the variable no_proxy followed by the target servers name. When you ssh into the jenkins node and check environment variables you also see this value set.
Now if I configure the within the jenkins job settings under execute shell to export the value no_proxy with the same values defined in what shows up under the environment variables and run the job it will connect to the server without proxy and the job will succeed. When I check the environment variables of that job, they are no different than the previous one that failed.