| 1 | From http://allmydata.org/pipermail/tahoe-dev/2009-December/003279.html: |
| 2 | |
| 3 | Note: These instructions omit the fact that you must install darcs as a prerequisite to setup a build slave. |
| 4 | |
| 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) |
| 25 | |
| 26 | This is also the part where you choose what sort of controls you want |
| 27 | to have over your buildslave. I would strongly advise you not to run |
| 28 | your buildslave under your user account, and (duh) not to give it any |
| 29 | sort of elevated privileges such as root! |
| 30 | |
| 31 | So, 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 |
| 33 | don't need to tell you this. |
| 34 | |
| 35 | Also you can use other mechanisms to lock it down more like jail, |
| 36 | chroot, etc. David Abrahams uses Solaris Zones to contain his |
| 37 | buildslaves. I don't know what particular features Zones offer. I |
| 38 | wonder if this means he can use ZFS snapshots to rewind the state of |
| 39 | the filesystem before running each build. That would be cool. Brian |
| 40 | Warner and the other buildbot maintainers have been hacking on some |
| 41 | tricks to set up your buildslaves inside a full virtual machine so |
| 42 | that you can have a pristine machine for every build -- e.g. "This is |
| 43 | a fresh install of OpenBSD 4.6 with nothing added except for buildbot |
| 44 | and its dependencies.". |
| 45 | |
| 46 | Personally I don't (yet) use any such fancy techniques -- I just run |
| 47 | my buildslaves under a separate user account which doesn't have |
| 48 | access to my personal stuff or to root privileges. |
| 49 | |
| 50 | Step 2: choose a name for your buildslave which will fit into the |
| 51 | list of buildslave names: http://allmydata.org/buildbot/buildslaves . |
| 52 | A hostname would be a good choice. |
| 53 | |
| 54 | Step 3: Receive a password from me in email. |
| 55 | |
| 56 | Step 4: create the buildslave with "buildbot create-slave $BASEDIR |
| 57 | dev.allmydata.com:9987 $SLAVENAME $PASSWORD" |
| 58 | |
| 59 | detailed docs: http://djmitche.github.com/buildbot/docs/0.7.11/ |
| 60 | #Creating-a-buildslave |
| 61 | |
| 62 | Then "buildbot start $BASEDIR". |
| 63 | |
| 64 | Step 5: Please do this two more times, one for pycryptopp and one for |
| 65 | zfec. Those two use the same $SLAVENAME and $PASSWORD and hostname |
| 66 | ("dev.allmydata.com"), but a different $BASEDIR (whatever directory |
| 67 | you want -- I personally use a different user account for my tahoe- |
| 68 | lafs, pycryptopp, and zfec buildslaves), and a different port |
| 69 | number. Port 9987 == tahoe-lafs, port 10998 == pycryptopp, port |
| 70 | 12987 == zfec . |
| 71 | |
| 72 | |
| 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 |
| 75 | passes unit tests on your platform. Eventually I would like to go on |
| 76 | to 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 |
| 79 | that 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 | }}} |