summaryrefslogtreecommitdiff
path: root/doc/onboarding.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/onboarding.texi')
-rw-r--r--doc/onboarding.texi13
1 files changed, 4 insertions, 9 deletions
diff --git a/doc/onboarding.texi b/doc/onboarding.texi
index f1376f9..b954f9a 100644
--- a/doc/onboarding.texi
+++ b/doc/onboarding.texi
@@ -272,11 +272,7 @@ be considered a recipe, rather than a fact.
Whenever a push occurs into one of Taler repositories, Buildbot gets
notified via the Git @emph{hooks} system.
-We use a patched version of the following Git hook [1].
-
-The patch allows the script to extract the @emph{project} keyword
-from the repository. Depending on this keyword, the Buildbot's
-scheduler will then perform or not the compilation.
+We use the hook in [1].
Following a @emph{gitolite}-policy, all the hook must be committed under
@code{gitolite-admin/local/hooks/repo-specific/post-receive.buildbot},
@@ -292,8 +288,8 @@ This is done by defining a @code{PBChangeSource} class in the following way:
@example
cs = changes.PBChangeSource(user='tony', passwd='hey')
@end example
-NOTE: those credentials must match the ones within the hook; search for the
-@code{UsernamePassoword} class in the hook.
+NOTE: those credentials must match the ones in the hook; change the top
+level variables @code{username} and @code{auth} in the hook to suit your setup.
The following line will finally "activate" the hook within the build master:
@example
@@ -305,8 +301,7 @@ and verify if there is a match with the @code{ChangeFilter} driving the schedule
If there is a match, the scheduler will fire its builders up, otherwise no action
is taken.
-[1]: @url{https://github.com/djmitche/buildbot/blob/d4ec886c3740a4f97a
-b172b81c9a9b94eb6f00d3/contrib/git_buildbot.py}.
+[1] @url{https://github.com/buildbot/buildbot-contrib/blob/master/master/contrib/git_buildbot.py}
@node Standalone deployment
@chapter Standalone deployment