Changes between Version 7 and Version 8 of BuildBot


Ignore:
Timestamp:
May 1, 2007 10:47:51 AM (7 years ago)
Author:
igloo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildBot

    v7 v8  
    1111First 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.li`).  You'll also need to decide: 
    1212 
    13   * when the build(s) should happen 
    14   * HEAD or branch builds 
     13  * when the build(s) should happen (time and timezone!) 
     14  * build HEAD, STABLE, or alternate between the two? 
    1515  * 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 
    1616 
    1717Finally, 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. 
    1818 
    19 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.  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. 
     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. 
    2020 
    2121Now create and enter the directory you want the buildbot client to work in