diff options
| author | James Moger <james.moger@gitblit.com> | 2011-12-27 17:50:39 -0500 |
|---|---|---|
| committer | James Moger <james.moger@gitblit.com> | 2011-12-27 17:50:39 -0500 |
| commit | d7905a15bf41df0574bd8613bf16f2d7ef0cb805 (patch) | |
| tree | a56487c8c018bbb097c4c395033d2f17aa9341cf /docs/01_setup.mkd | |
| parent | 0fb1fd48c430d5dbb61485a9a6c6f52aac200e09 (diff) | |
| download | gitblit-d7905a15bf41df0574bd8613bf16f2d7ef0cb805.tar.gz gitblit-d7905a15bf41df0574bd8613bf16f2d7ef0cb805.zip | |
Implemented Team hook scripts
Diffstat (limited to 'docs/01_setup.mkd')
| -rw-r--r-- | docs/01_setup.mkd | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/docs/01_setup.mkd b/docs/01_setup.mkd index e400a0b1..5a3336b2 100644 --- a/docs/01_setup.mkd +++ b/docs/01_setup.mkd @@ -196,6 +196,7 @@ The `users.conf` file uses a Git-style configuration format: user = babaracus
repository = topsecret.git
mailingList = list@ateam.org
+ postReceiveScript = sendmail
The `users.conf` file allows flexibility for adding new fields to a UserModel object that the original `users.properties` file does not afford without imposing the complexity of relying on an embedded SQL database.
@@ -251,13 +252,14 @@ The Groovy hook mechanism allows for dynamic extension of Gitblit to execute cus 3. Script filenames must not have spaces!
4. Scripts must be explicitly specified to be executed, no scripts are *automatically* executed by name or extension.
5. A script can be specified to run on *all repositories* by adding the script file name to *groovy.preReceiveScripts* or *groovy.postReceiveScripts* in `gitblit.properties` or `web.xml`.
-6. Scripts may also be specified per-repository in the repository's settings.
-7. Globally specified scripts are excluded from the list of available scripts in a repository's settings
-8. Globally specified scripts are executed first, in their listed order, followed by per-repository scripts, in their listed order.
-9. A script may only be defined once in a pre-receive chain and once in a post-receive chain.
+6. Scripts can be specified for a team.
+7. Scripts may also be specified per-repository in the repository's settings.
+8. Globally-specified scripts and team-specified scripts are excluded from the list of available scripts in a repository's settings
+9. Globally-specified scripts are executed first, in their listed order; followed by team-specified scripts in their listed order by alphabetical team order; followed by per-repository scripts, in their listed order.
+10. A script may only be defined once in a pre-receive chain and once in a post-receive chain.
You may execute the same script on pre-receive and post-receive, just not multiple times within a pre-receive or post-receive event.
-10. Gitblit does not differentiate between what can be a pre-receive script and what can be a post-receive script.
-11. If a script *returns false* then the hook chain is aborted and none of the subsequent scripts will execute.
+11. Gitblit does not differentiate between what can be a pre-receive script and what can be a post-receive script.
+12. If a script *returns false* then the hook chain is aborted and none of the subsequent scripts will execute.
Some sample scripts are included in the GO and WAR distributions to show you how you can tap into Gitblit with the provided bound variables. Additional implementation details may be specified in the header comment of these examples.
|