tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

new improved instructions 

[Imported from Trac: page HowtoContributeABuildbot, version 3]
zooko 2010-06-25 01:14:27 +00:00
parent dcf6d4f92d
commit 354fb199bb
1 changed files with 16 additions and 50 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

64
HowtoContributeABuildbot.md

@ -1,27 +1,8 @@
From <http://tahoe-lafs.org/pipermail/tahoe-dev/2009-December/003279.html>: From <http://tahoe-lafs.org/pipermail/tahoe-dev/2009-December/003279.html> . Subsequently updated.
Note: These instructions omit the fact that you must install darcs as a prerequisite to setup a build slave. Step 1: install darcs. Start at <http://wiki.darcs.net/Binaries> .
``` Step 2: install buildbot on your system
[tahoe-dev] How to set up a buildslave?
Zooko Wilcox-O'Hearn zooko at zooko.com
Sun Dec 6 11:25:27 PST 2009
* Previous message: [tahoe-dev] How to set up a buildslave?
* Next message: [tahoe-dev] [tahoe-lafs] #534: "tahoe cp" command encoding issue
* Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sunday, 2009-12-06, at 11:27 , <kyle at arbyte.us> wrote:
> I would like to set up my openbsd/amd64 system to be a buildslave.
> How do I do this?
I'll summarize to tahoe-dev, and then let's take the back-and-forth
details of the setup into private mail so as not to bore the non-
buildbot-operating mailing list readers.
Step 1: install buildbot on your system (presumably using the OpenBSD
port)
This is also the part where you choose what sort of controls you want This is also the part where you choose what sort of controls you want
to have over your buildslave. I would strongly advise you not to run to have over your buildslave. I would strongly advise you not to run
@ -29,7 +10,7 @@ your buildslave under your user account, and (duh) not to give it any
sort of elevated privileges such as root! sort of elevated privileges such as root!
So, running under a separate user account without high privileges is So, running under a separate user account without high privileges is
definitely a good idea, but since you're an OpenBSD user I guess I definitely a good idea, but since you're a security-aware user I guess I
don't need to tell you this. don't need to tell you this.
Also you can use other mechanisms to lock it down more like jail, Also you can use other mechanisms to lock it down more like jail,
@ -47,45 +28,30 @@ Personally I don't (yet) use any such fancy techniques -- I just run
my buildslaves under a separate user account which doesn't have my buildslaves under a separate user account which doesn't have
access to my personal stuff or to root privileges. access to my personal stuff or to root privileges.
Step 2: choose a name for your buildslave which will fit into the Step 3: choose a name for your buildslave which will fit into the
list of buildslave names: http://allmydata.org/buildbot/buildslaves . list of buildslave names: <http://allmydata.org/buildbot/buildslaves> .
A hostname would be a good choice. A hostname would be a good choice.
Step 3: Receive a password from me in email. Step 4: Receive a password from me in email.
Step 4: create the buildslave with "buildbot create-slave $BASEDIR Step 5: create the buildslave with `buildbot create-slave $BASEDIR dev.allmydata.org:9987 $SLAVENAME $PASSWORD`
dev.allmydata.com:9987 $SLAVENAME $PASSWORD"
detailed docs: http://djmitche.github.com/buildbot/docs/0.7.11/ detailed docs: <http://djmitche.github.com/buildbot/docs/latest/Creating-a-buildslave.html#Creating-a-buildslave>
#Creating-a-buildslave
Then "buildbot start $BASEDIR". Then `buildbot start $BASEDIR`.
Step 5: Please do this two more times, one for pycryptopp and one for Step 6: Please do this two more times, one for pycryptopp and one for
zfec. Those two use the same $SLAVENAME and $PASSWORD and hostname zfec. Those two use the same $SLAVENAME and $PASSWORD and hostname
("dev.allmydata.com"), but a different $BASEDIR (whatever directory ("dev.allmydata.org"), but a different $BASEDIR (whatever directory
you want -- I personally use a different user account for my tahoe- you want -- I personally use a different user account for my tahoe-
lafs, pycryptopp, and zfec buildslaves), and a different port lafs, pycryptopp, and zfec buildslaves), and a different port
number. Port 9987 == tahoe-lafs, port 10998 == pycryptopp, port number. Port 9987 == tahoe-lafs, port 10998 == pycryptopp, port
12987 == zfec . 12987 == zfec .
Okay, once you've gotten all this working then we'll see your OpenBSD/ Okay, 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
amd64 machine on the buildbot pages and we'll see how well Tahoe-LAFS
passes unit tests on your platform. Eventually I would like to go on passes unit tests on your platform. Eventually I would like to go on
to the next step, which is integrating Tahoe-LAFS into the official to the next step, which is integrating Tahoe-LAFS into the official
OpenBSD package system (ports) and adding tests to check whether package system of your operating system and adding tests to check whether
Tahoe-LAFS is still correctly building from its ports package. But Tahoe-LAFS is still correctly building from its package. But
that is for another day. that is for another day.
Regards,
Zooko
* Previous message: [tahoe-dev] How to set up a buildslave?
* Next message: [tahoe-dev] [tahoe-lafs] #534: "tahoe cp" command encoding issue
* Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the tahoe-dev mailing list
```