[Imported from Trac: page HowtoContributeABuildbot, version 27]
parent
c62ebddd00
commit
65813d5de9
|
@ -9,9 +9,6 @@ A buildslave makes TCP connections to the buildmaster, which `tahoe-lafs.org` op
|
|||
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
|
||||
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.
|
||||
|
||||
## Name The Buildslave
|
||||
Choose a name for your buildslave which will fit into the list of buildslave names: [//buildbot-tahoe-lafs/buildslaves].
|
||||
A hostname would be a good choice.
|
||||
|
@ -36,3 +33,6 @@ Okay, once you've gotten all this working then we'll see your machine on the [//
|
|||
|
||||
### More Details
|
||||
The official buildslave creation documentation is [here](http://djmitche.github.com/buildbot/docs/latest/Creating-a-buildslave.html#Creating-a-buildslave).
|
||||
|
||||
#### 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.
|
||||
|
|
Loading…
Reference in a new issue