[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [taler-deployment] branch master updated: update hook instr
From: |
gnunet |
Subject: |
[GNUnet-SVN] [taler-deployment] branch master updated: update hook instructions |
Date: |
Thu, 19 Oct 2017 15:28:59 +0200 |
This is an automated email from the git hooks/post-receive script.
marcello pushed a commit to branch master
in repository deployment.
The following commit(s) were added to refs/heads/master by this push:
new 2a9592f update hook instructions
2a9592f is described below
commit 2a9592f85b7fd97a447cac8bf22403dc7e2efbeb
Author: Marcello Stanisci <address@hidden>
AuthorDate: Thu Oct 19 15:28:42 2017 +0200
update hook instructions
---
doc/onboarding.texi | 13 ++++---------
1 file 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
address@hidden 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
--
To stop receiving notification emails like this one, please contact
address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [taler-deployment] branch master updated: update hook instructions,
gnunet <=