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

[Imported from Trac: page HowtoContributeABuildbot, version 17]

arch_o_median 2011-01-04 19:10:38 +00:00
parent ec260b8949
commit d78ed9e65b
1 changed files with 3 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
HowtoContributeABuildbot.md

@ -24,18 +24,10 @@ Those three use the same $SLAVENAME, $PASSWORD and hostname, but a different $BA
For the $BASEDIR your can use whatever directory you want.
Use a different user account for my tahoe-lafs, pycryptopp, and zfec buildslaves.
## Detailed Documentation
Detailed docs: <http://djmitche.github.com/buildbot/docs/latest/Creating-a-buildslave.html#Creating-a-buildslave>
Use a different user account for tahoe-lafs, pycryptopp, and zfec buildslaves.
Then `buildbot start $BASEDIR`.
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 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 package system of your operating system and adding tests to check whether Tahoe-LAFS is still correctly building from its package. But that is for another day.
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
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
package system of your operating system and adding tests to check whether
Tahoe-LAFS is still correctly building from its package. But
that is for another day.
Detailed docs: <http://djmitche.github.com/buildbot/docs/latest/Creating-a-buildslave.html#Creating-a-buildslave>