Changes between Version 2 and Version 3 of BuildBot


Ignore:
Timestamp:
Feb 2, 2007 4:03:25 PM (7 years ago)
Author:
simonmar
Comment:

updates

Legend:

Unmodified
Added
Removed
Modified
  • BuildBot

    v2 v3  
    1 == Setting up a nightly build == 
     1= Setting up a nightly build = 
    22 
    3 === Common steps === 
     3The GHC buildbot builds GHC on various platforms in various different ways each night, runs the test suite and performance benchmarks, and mails the results to the `cvs-ghc@haskell.org` mailing list.  We're always keen to add more build slaves to the setup, especially if you have a platform that doesn't already have a build slave, so if you'd like to join the fun, please let us know at [mailto:cvs-ghc@haskell.org].  If a platform is represented in the nightly builds, it's more likely we'll be able to identify and fix problems specific to that platform quickly. 
    44 
    5 First you, as a buildbot client, need to agree a buildbot username (`myUser`) and password (`myPass`) with the buildbot admins. You'll also need to decide when the builds should happen. Finally, if there is anything special that needs to be done for the client (e.g. if gcc is in an unusual place) then you'll need to let the admins know. 
     5To see the current status of the builds: 
    66 
    7 === Client steps === 
     7  [http://darcs.haskell.org:8010/] 
    88 
    9 Then you'll need to install buildbot and its dependencies on the machine that will be doing the nightly build; see the [http://buildbot.sourceforge.net/ BuildBot website] for details. 
     9== To create a new build slave == 
     10 
     11First you, as a buildbot client, need to agree a buildbot username (`myUser`) and password (`myPass`) with the buildbot admins (just pick a username and password and send it to `igloo@earth.il`).  You'll also need to decide: 
     12 
     13  * when the build(s) should happen 
     14  * HEAD or branch builds 
     15  * full build (up to stage 3, with extra-libs, full testsuite, and 5 nofib runs) or a fast build (stage 2, no extra-libs, fast testsuite, no nofib runs), or something in-between 
     16 
     17Finally, if there is anything special that needs to be done for the client (e.g. if gcc is in an unusual place) then you'll need to let the admins know. 
     18 
     19Then you'll need to install buildbot and its dependencies on the machine that will be doing the nightly build; see the [http://buildbot.sourceforge.net/ BuildBot website] for details.  NB. if you're on Windows, you'll need to install BuildBot under Cygwin using the Cygwin Python; there are various problems getting the GHC build to work via BuildBot using the native Win32 Python, so we've given up on that route for now. 
    1020 
    1121Now create and enter the directory you want the buildbot client to work in 
     
    2232It also created `Makefile.sample`; we recommend renaming this to `Makefile`. You can now start the buildbot client with `make start` and stop it with `make stop`. 
    2333 
    24 === Admin steps === 
     34You can watch what your slave is doing by looking at the `twistd.log` file in the directory in which you're running your slave. 
     35 
     36== Admin steps == 
     37 
     38(for the admins only...) 
    2539 
    2640Pull the buildbot master configuration: 
     
    3145}}} 
    3246 
    33 Edit `master.cfg`. Search for `slaves` and you should find a list containing an entry for each slave. Add an entry to the list like 
    34 {{{ 
    35 { 'user': 'myUser', 
    36   'pass': 'myPass', 
    37   'factory': ghcDefaultFactory }, 
    38 }}} 
    39 If it is a Windows machine then use `ghcDefaultWindowsFactory` instead (this just tells it to use the correct configure options for Windows). 
    40  
    41 Now search for `schedulers` and either add `myUser` to the `builderNames` of an existing scheduler or, if there isn't one that runs at the time that you want, add a new scheduler. 
    42  
    43 Record and push the changes.  Then restart the build master: 
     47Edit `master.cfg`.  Add new entries to `slaves`, `schedulers`, and `builders` as necessary.  Record and push the changes.  Then restart the build master: 
    4448 
    4549{{{ 
     
    4751}}} 
    4852 
    49 If there is anything unusual about the machine the build is being run on, e.g. the path to `gcc` is different, then you will need to add a field for the unusual thing to GhcDefaultConfig and alter the build steps to make use of it. Then make a special factory for the build client you are adding with this field changed as appropriate. 
     53If there is anything unusual about the machine the build is being run on, e.g. the path to `gcc` is different, then you will need to add a field for the unusual thing to !GhcDefaultConfig and alter the build steps to make use of it. Then make a special factory for the build client you are adding with this field changed as appropriate. 
    5054 
    51 === Did it work? === 
     55== Did it work? == 
    5256 
    5357Once the master is reconfiged and the client is started, the client should become visible on