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

[Imported from Trac: page HowtoContributeABuildbot, version 9]

arch_o_median 2011-01-04 18:46:07 +00:00
parent b459583f22
commit 76f007d891
1 changed files with 5 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
HowtoContributeABuildbot.md

@ -3,29 +3,14 @@
## Configuration ## Configuration
This is also the part where you choose what sort of controls you want Create a user account with low privileges to run buildbot.
to have over your buildslave. I would strongly advise you not to run
your buildslave under your user account, and (duh) not to give it any
sort of elevated privileges such as root!
So, running under a separate user account without high privileges is ### Optional Configurations
definitely a good idea, but since you're a security-aware user I guess I You can use other mechanisms to lock buildbot down like jail,
don't need to tell you this.
Also you can use other mechanisms to lock it down more like jail,
chroot, etc. David Abrahams uses Solaris Zones to contain his chroot, etc. David Abrahams uses Solaris Zones to contain his
buildslaves. I don't know what particular features Zones offer. I buildslaves. Brian Warner and the other buildbot maintainers have been hacking on some
wonder if this means he can use ZFS snapshots to rewind the state of
the filesystem before running each build. That would be cool. Brian
Warner and the other buildbot maintainers have been hacking on some
tricks to set up your buildslaves inside a full virtual machine so tricks to set up your buildslaves inside a full virtual machine so
that you can have a pristine machine for every build -- e.g. "This is that you can have a pristine machine for every build.
a fresh install of OpenBSD 4.6 with nothing added except for buildbot
and its dependencies.".
Personally I don't (yet) use any such fancy techniques -- I just run
my buildslaves under a separate user account which doesn't have
access to my personal stuff or to root privileges.
Step 3: 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://tahoe-lafs.org/buildbot/buildslaves> . list of buildslave names: <http://tahoe-lafs.org/buildbot/buildslaves> .