From: Todd Lyons Date: Tue, 3 Jun 2014 12:09:41 +0000 (-0700) Subject: Updated Installation (markdown) X-Git-Url: https://git.exim.org/buildfarm-client-wiki.git/commitdiff_plain/05eea3e9f1a7e6a96f1eaa02b88c940cb51097b9?ds=sidebyside Updated Installation (markdown) --- diff --git a/Installation.md b/Installation.md index a4a1863..0a0cf1c 100644 --- a/Installation.md +++ b/Installation.md @@ -1,9 +1,9 @@ # Installing Exim BuildFarm Client So you want to give back to the Exim project but don't know how? Being a member of the Exim BuildFarm is one way you can help. If your distro and version is not on the list that is currently being built, or if your build configuration is drastically different than others with your distro and version, then please consider submitting a request to join the farm. I would also like to point out that the Debian project has excellent Exim coverage on their Experimental [Build Farm](https://buildd.debian.org/status/package.php?p=exim4&suite=experimental). We're not discouraging you from joining the Exim BuildFarm if you're Debian or Debian derivative, but merely want to acknowledge the excellent job the Debian project already does with it. -This Installation page works on the assumption that you have already submitted your [Exim BuildFarm Application](http://eximbuild.mrball.net/cgi-bin/register-form.pl) and the BuildFarm administration has sent you an email with your machine alias (aka _animal_) and secret password, which you will enter in step 9 below. If you just want to run the build farm client and never submit the results, you call simply run everything with the --test option and it will still work. If you ever run it without --test, it will still work, but the server will reject the feedback because it's from an unknown _animal_. +You will need to submit an [Exim BuildFarm Application](http://eximbuild.mrball.net/cgi-bin/register-form.pl) and the BuildFarm administration has sent you an email with your machine alias (aka _animal_) and secret password, which you will enter in step 9 below. If you just want to run the build farm client and never submit the results, you call simply run everything with the --test option and it will go through all defined build/test steps without saving the state anywhere. In that case, if you accidentally run it without --test, the build process will still work, but the build state will be locally recorded, and when the stated is submitted to the server, it will reject the feedback because it's from an unknown _animal_. -If you want to run more than one instance of the build farm to test multiple different configurations, such as one with OpenSSL and one with GnuTLS, for each subsequent animal simply start at step 9. More details on the extra configuration required to keep it separate from the main build are at the end of this page. +If you want to run more than one instance of the build farm to test multiple different configurations, such as one with OpenSSL and one with GnuTLS, make a copy of the *build-farm.conf* template for each subsequent animal simply start at step 9. More details on the extra configuration required to keep it separate from the main build are at the end of this page. ## Install Steps 1. Make sure that all required packages for Exim to build successfully are installed. The minimal package requirements are the basic suite of compiler tools and basic libraries. You will also need to install the ccache package. @@ -52,7 +52,7 @@ Once that works properly, then the cron command changes to: 
6 * * * * ssh -tt farm@localhost $HOME/bin/build_farm.sh
## 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: +As mentioned above, you can start at step 9 for each additional build you'll do on the same machine. A second application must be filled out to put the appropriate data in the database because this is treated a separate BuildFarm client: 1. Make a second copy of the *build-farm.conf* with a different name, such as *build-farm-alias2.conf*. 2. Set the path for build_root and the CCACHE_DIR environment settings, each to a new subdirectory from the first configuration.