jenkins on Mac, PATH is not set right, no /usr/loc

问题:

I recently installed Jenkins, using Homebrew. I also installed Mercurial using Homebrew.

I can successfully clone an hg repo just fine - from Terminal. But if I try and do the same thing as part of a job in Jenkins, it fails.

So, in by job, I told Jenkins to run a shell script echo $PATH. Sure enough, the path /usr/local/bin is not there. If I execute the same command from Terminal, it's there.

So, what is the best way to modify PATH so that Jenkins is pulling the same PATH that I'm using, when I echo it from Terminal?

Note, Jenkins is running from the same user account that I'm logged into doing these tests, so I can't fathom why this is happening.

回答1:

In your launchd .plist file for Jenkins, you can set the PATH environment variable by using the following:

<key>EnvironmentVariables</key>
<dict>
    <key>PATH</key>
    <string>(insert your path value here)</string>
</dict>

That should set the PATH to whatever you need.

回答2:

For some reason, Jenkins doesn't keep /usr/local/bin in the PATH when connecting to a slave.
You can add it to the PATH either by

• Adding an environment variable on the Node Configuration, or

• Adding a .bashrc file on the user folder with

  PATH="/usr/local/bin:${PATH}"
  

回答3:

You can set PATH in launchd.conf file. See here for details. Note that man launchctl says that 'commands can be stored in $HOME/.launchd.conf or /etc/launchd.conf to be read at the time launchd starts', so you probably can create '.launchd.conf' in your home directory and use instructions from the link with this file. But as far as I know in launchd.conf file you can't add directory to PATH, you can just rewrite PATH.
You can also see here for the solution using /etc/paths.d directory

回答4:

I found that even setting the PATH environment variable for the node didn't work for the hombrew Mercurial installation. The path WOULD get set, but only for the script build phase, not for the VCS checkout phase. Here's what I wound up doing.

1. Go into Manage Jenkins -> Configure System
2. Add a new Mercurial Installation
3. Name it whatever you want (I named mine build-mac)
4. For Installation Directory I put /usr/local
5. The Executable parameter was pre-set to INSTALLATION/bin/hg, so I just left it at that.
6. Everything else in here can be left blank
7. Go into your job and edit the configuration
8. Under Source Code Management set Mercurial Version to the mercurial installation you just added.
9. Save
10. $$$

Hope that helps anyone else running into this same problem, now that we're not allowed (by default anyways) to do anything inside of /usr/bin anymore. Previously I would have just symlinked hg there, but now with the new "System Integrity Protection" "feature", that's no longer as trivial of task, and even more difficult if your Mac slave is headless.