|
|
|
Noticed that PATH set in /etc/launchd.conf is, indeed picked up by QuickBuild agent.
If specified with /etc/paths.d/* files, /etc/profile, .profile PATH is not picked up by QuickBuild agent. See below reply from JSW support:
I did some more poking around and found the following two pages: http://stackoverflow.com/questions/135688/setting-environment-variables-in-os-x http://superuser.com/questions/476752/setting-environment-variables-in-os-x-for-gui-applications As is true with most "experts" pages, there is a wide range of advice, but it looks like /etc/launchd.conf is the option which works. This appears to be in line with what you are seeing. There does indeed appear to be several differences between OS versions. Are you seeing the problems after a reboot? new processes don't reliably pick up most env changes because of the way the environments are managed. It looks like an OS reboot or at least logging out and back in is usually needed. I also came across this: http://diaryproducts.net/EnvPane Is there some specific behavior that you think the Wrapper should be doing differently? From what I have seen the behavior appears to be normal for each OS version. There may be some things we can do to make the Wrapper more convenient for users, but I would have to understand the issues very well to make sure we don't introduce any problems. Thank you very much, Robin for the detailed response.
My main problem is that PATH is inconsistent while switching between service mode and console mode. This complicates debugging. |
Actually the problem is seen on 3 newer MacOSX: 10.7, 10.8, 10.9.
The problem is not seen on 2 older MacOSX: 10.5 and 10.6.