[Imported from Trac: page HowtoContributeABuildbot, version 26]
parent
de3f2da0a8
commit
c62ebddd00
|
@ -5,7 +5,9 @@ You'll need [git](http://git-scm.com/) and [buildbot-slave](http://trac.buildbot
|
||||||
A buildslave makes TCP connections to the buildmaster, which `tahoe-lafs.org` operates. You do not need a publicly routable IP address.
|
A buildslave makes TCP connections to the buildmaster, which `tahoe-lafs.org` operates. You do not need a publicly routable IP address.
|
||||||
|
|
||||||
## Configuration
|
## Configuration
|
||||||
Create a user account with low privileges to run buildbot.
|
|
||||||
|
Anyone who can get their code into any part of the development repos, can take control the of the user account running the buildslave process.
|
||||||
|
Therefore, create a dedicated user account to run this process.
|
||||||
|
|
||||||
#### Optional Configurations
|
#### Optional Configurations
|
||||||
You can use other mechanisms to limit the privileges available to the buildbot, 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 (see below) separated.
|
You can use other mechanisms to limit the privileges available to the buildbot, 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 (see below) separated.
|
||||||
|
|
Loading…
Reference in a new issue