From c4f64e059f107a3b5fe269b1d44b8e852a3b1b9e Mon Sep 17 00:00:00 2001 From: "Heiko Schlittermann (HS12-RIPE)" Date: Tue, 1 Nov 2016 23:52:25 +0100 Subject: [PATCH] Update crontab hint --- Installation.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Installation.md b/Installation.md index 5c637f8..0ecc113 100644 --- a/Installation.md +++ b/Installation.md @@ -39,10 +39,9 @@ This will create the repo checkout in the directory *~/code/*. 16. If you enabled the documentation building process in the *build-farm.conf*, then you can try to build it with `./run_build --test --verbose=2 --only-steps=configure,make-doc`. For documentation generation to succeed, it will require extra packages to be installed to support xml, xslt, pdf, and a few other things. Please see the comments on the [Building Documentation](./BuildingDocs.html) page. 17. If you can get past each of these steps, then your build farm system meets the minimum requirements. 18. The official process can be kicked off by running `/home/farm/code/run_cron --run-all`. This will run the default build configuration, keep track of the git repository status, and upload the build results to the server. -19. 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 2 hours. If a previous instantiation is still running, the script will detect the lockfile and exit so as not to step on each other. I had a problem running the *run_cron* script in that cron gives a highly sanitized path to the script when it runs it. I made a second script to call the first one so I could insert path elements in that were needed: +19. 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 2 hours. If a previous instantiation is still running, the script will detect the lockfile and exit so as not to step on each other. *Caution* Cron provides a highly sanitized environment to the run_cron script. Depending on your cron version you may supply a `PATH=…` line in your crontab, or you need to call a wrapper script around `run_cron`: ```` - $ 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 $@ -- 2.30.2