To check their respective environment variables, visit http: //server/jenkins/computer/COMPUTERNAME/systemInfo. Many tools also change their behaviours on the values/presence/absence of some environment variables, so you might want to check those, aside from PATH.Įach slave also gets different environment variables, depending on how it's started. To check what environment variables Jenkins is seeing, go to http: //server/jenkins/systemInfo and scroll down to see the environment variables. PATH / Environment variablesĮspecially when you run Jenkins as a service/daemon under a different user account, it often gets a different PATH environment variable than your shell does, and this results in failing to find some commands, or invoking different versions of the same commands. So before you suspect a bug in Jenkins, please go through the following check list. ![]() Often, your build is sensitive to the environment in an unintended way and that causes a build failure.
0 Comments
Leave a Reply. |