Changes between Version 2 and Version 3 of HowtoContributeABuildbot


Ignore:
Timestamp:
2010-06-25T01:14:27Z (14 years ago)
Author:
zooko
Comment:

new improved instructions

Legend:

Unmodified
Added
Removed
Modified
  • HowtoContributeABuildbot

    v2 v3  
    1 From http://tahoe-lafs.org/pipermail/tahoe-dev/2009-December/003279.html:
     1From http://tahoe-lafs.org/pipermail/tahoe-dev/2009-December/003279.html . Subsequently updated.
    22
    3 Note: These instructions omit the fact that you must install darcs as a prerequisite to setup a build slave.
     3Step 1: install darcs. Start at http://wiki.darcs.net/Binaries .
    44
    5 {{{
    6 [tahoe-dev] How to set up a buildslave?
    7 Zooko Wilcox-O'Hearn zooko at zooko.com
    8 Sun Dec 6 11:25:27 PST 2009
    9 
    10     * Previous message: [tahoe-dev] How to set up a buildslave?
    11     * Next message: [tahoe-dev] [tahoe-lafs] #534: "tahoe cp" command encoding issue
    12     * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
    13 
    14 On Sunday, 2009-12-06, at 11:27 , <kyle at arbyte.us> wrote:
    15 
    16 > I would like to set up my openbsd/amd64 system to be a buildslave.   
    17 > How do I do this?
    18 
    19 I'll summarize to tahoe-dev, and then let's take the back-and-forth 
    20 details of the setup into private mail so as not to bore the non-
    21 buildbot-operating mailing list readers.
    22 
    23 Step 1: install buildbot on your system (presumably using the OpenBSD 
    24 port)
     5Step 2: install buildbot on your system
    256
    267This is also the part where you choose what sort of controls you want 
     
    3011
    3112So, running under a separate user account without high privileges is 
    32 definitely a good idea, but since you're an OpenBSD user I guess I 
     13definitely a good idea, but since you're a security-aware user I guess I 
    3314don't need to tell you this.
    3415
     
    4829access to my personal stuff or to root privileges.
    4930
    50 Step 2: choose a name for your buildslave which will fit into the 
     31Step 3: choose a name for your buildslave which will fit into the 
    5132list of buildslave names: http://allmydata.org/buildbot/buildslaves . 
    5233A hostname would be a good choice.
    5334
    54 Step 3: Receive a password from me in email.
     35Step 4: Receive a password from me in email.
    5536
    56 Step 4: create the buildslave with "buildbot create-slave $BASEDIR 
    57 dev.allmydata.com:9987 $SLAVENAME $PASSWORD"
     37Step 5: create the buildslave with {{{buildbot create-slave $BASEDIR dev.allmydata.org:9987 $SLAVENAME $PASSWORD}}}
    5838
    59 detailed docs: http://djmitche.github.com/buildbot/docs/0.7.11/
    60 #Creating-a-buildslave
     39detailed docs: http://djmitche.github.com/buildbot/docs/latest/Creating-a-buildslave.html#Creating-a-buildslave
    6140
    62 Then "buildbot start $BASEDIR".
     41Then {{{buildbot start $BASEDIR}}}.
    6342
    64 Step 5: Please do this two more times, one for pycryptopp and one for 
     43Step 6: Please do this two more times, one for pycryptopp and one for 
    6544zfec.  Those two use the same $SLAVENAME and $PASSWORD and hostname 
    66 ("dev.allmydata.com"), but a different $BASEDIR (whatever directory 
     45("dev.allmydata.org"), but a different $BASEDIR (whatever directory 
    6746you want -- I personally use a different user account for my tahoe-
    6847lafs, pycryptopp, and zfec buildslaves), and a different port 
     
    7150
    7251
    73 Okay, once you've gotten all this working then we'll see your OpenBSD/
    74 amd64 machine on the buildbot pages and we'll see how well Tahoe-LAFS 
     52Okay, once you've gotten all this working then we'll see your machine on the buildbot pages and we'll see how well Tahoe-LAFS 
    7553passes unit tests on your platform.  Eventually I would like to go on 
    7654to the next step, which is integrating Tahoe-LAFS into the official 
    77 OpenBSD package system (ports) and adding tests to check whether 
    78 Tahoe-LAFS is still correctly building from its ports package.  But 
     55package system of your operating system and adding tests to check whether 
     56Tahoe-LAFS is still correctly building from its package.  But 
    7957that is for another day.
    80 
    81 
    82 Regards,
    83 
    84 Zooko
    85 
    86     * Previous message: [tahoe-dev] How to set up a buildslave?
    87     * Next message: [tahoe-dev] [tahoe-lafs] #534: "tahoe cp" command encoding issue
    88     * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
    89 
    90 More information about the tahoe-dev mailing list
    91 }}}