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

Add a link to Buildbot Output and Policy. 

[Imported from Trac: page HowtoContributeABuildbot, version 33]
nejucomo 2014-08-23 20:47:24 +00:00
parent dc02cc882b
commit 9090cb0b7a
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
HowtoContributeABuildbot.md

@ -1,3 +1,5 @@
Contributing a buildbot improves the quality of Tahoe-LAFS and also is integral to defining out supported platforms, as described in [Buildbot Policy](BuildbotPolicy). You can see the results of our builtbot network in the [//buildbot-tahoe-lafs the Buildbot output page].
## Prerequisites
You'll need [git](http://git-scm.com/) and [buildbot-slave](http://trac.buildbot.net/wiki/DownloadInstall) before you can proceed.
@ -32,4 +34,4 @@ Then `buildbot start $BASEDIR`.
Okay, once you've gotten all this working then we'll see your machine on the [//buildbot-tahoe-lafs/waterfall?show_events=true buildbot pages] and we'll see how well Tahoe-LAFS passes unit tests on your platform.
#### Optional Configurations
You can use other mechanisms to limit the privileges available to the buildslave process/account, such as jail, chroot, or Solaris Zones. You can optionally use a different user account or other privilege-limiting mechanisms to keep the tahoe-lafs, pycryptopp, and zfec buildslaves separated from each other.
You can use other mechanisms to limit the privileges available to the buildslave process/account, such as jail, chroot, or Solaris Zones. You can optionally use a different user account or other privilege-limiting mechanisms to keep the tahoe-lafs, pycryptopp, and zfec buildslaves separated from each other.