From 60a3ca9f02e3ba4d9054cc0720e9f521278a571e Mon Sep 17 00:00:00 2001 From: Todd Lyons Date: Tue, 29 Oct 2013 13:53:27 -0700 Subject: [PATCH 1/1] Mention cron sanitizes PATH --- Installation.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Installation.md b/Installation.md index 22f1ce6..d0c313d 100644 --- a/Installation.md +++ b/Installation.md @@ -31,6 +31,11 @@ This will create the repo checkout in the directory *~/code/*. 16. If you can get past each of these steps, then your build farm system meets the minimum requirements. 17. The official process can be kicked off by running `/home/farm/code/run_cron.sh --run-all`. This will run the default build configuration, keep track of the git repository status, and upload the build results to the server. 18. Once that command runs with no complaints, add it to the **farm** user crontab. You can run it at whatever frequency you choose, I suggest 1 hour. If a previous instantiation is still running, the script will detect the lockfile and exit so as not to step on each other. +19. I found that running the *run_cron.sh* had a problem in that cron provides a sanitized path to the script when it gets run. I made a second wrapper script to call the first one so I could put path elements in that were needed: + $ more /home/farm/bin/build_farm.sh + #!/bin/bash + export PATH="/usr/local/bin:/sbin:/usr/sbin:$PATH" + $HOME/code/run_cron.sh --run-all $@ ## Multiple build clients on one machine As mentioned above, you can start at step 9. A second application must be filled out to put the appropriate data in the database because this is treated a separate BuildFarm client: -- 2.30.2