From 4d64b7556fa62eb95911330da6264a287ff1f47c Mon Sep 17 00:00:00 2001 From: Todd Lyons Date: Tue, 22 Oct 2013 13:43:43 -0700 Subject: [PATCH] Add required argument to run_cron.sh --- Installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Installation.md b/Installation.md index 01bbfd9..9dd6eeb 100644 --- a/Installation.md +++ b/Installation.md @@ -24,7 +24,7 @@ This will create the repo checkout in the directory *~/code/*. 14. Test the test suite by running `./run_build.pl --test --verbose=2 --only-steps=configure,make,test --override range_num_tests='1 2'`. If there are build errors when building the test suite, or runtime errors trying to run the test suite, you may need to install additional packages (you shouldn't though). 15. If you enabled the documentation building process in the *build-farm.conf*, then you can try to build it with `./run_build.pl --test --verbose=2 --only-steps=configure,build_docs`. For documentation generation to succeed, it will require extra packages to be installed to support xml, xslt, pdf, and a few other things. 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`. This will run the default build configuration, keep track of the git repository status, and upload the build results to the server. +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. ## Overview -- 2.30.2