From d78ed9e65b401544b46af5d67deb75e8cdb150f9 Mon Sep 17 00:00:00 2001 From: arch_o_median <> Date: Tue, 4 Jan 2011 19:10:38 +0000 Subject: [PATCH] [Imported from Trac: page HowtoContributeABuildbot, version 17] --- HowtoContributeABuildbot.md | 14 +++----------- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/HowtoContributeABuildbot.md b/HowtoContributeABuildbot.md index 659d6b9..b9d34f7 100644 --- a/HowtoContributeABuildbot.md +++ b/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: +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. \ No newline at end of file +Detailed docs: