| | |
|---|
| | |
|
|---|
| | | *SINCE 0.8.0*
|
|---|
| | |
|
|---|
| | | The preferred hook mechanism is Groovy. This mechanism only executes when pushing to Gitblit, not when pushing to some other Git tooling in your stack.
|
|---|
| | | Gitblit uses Groovy for its push hook mechanism. This mechanism only executes when pushing to Gitblit, not when pushing to some other Git tooling in your stack.
|
|---|
| | |
|
|---|
| | | The Groovy hook mechanism allows for dynamic extension of Gitblit to execute custom tasks on receiving and processing push events. The scripts run within the context of your Gitblit instance and therefore have access to Gitblit's internals at runtime.
|
|---|
| | |
|
|---|
| | |
|---|
| | | ### Enabling Push Notifications
|
|---|
| | |
|
|---|
| | | In order to send email notifications on a push to Gitblit, this script must be specified somewhere in the *post-receive* script chain.
|
|---|
| | | You may specify *sendmail* in one of two places:
|
|---|
| | | You may specify *sendmail* in one of three places:
|
|---|
| | |
|
|---|
| | | 1. *groovy.postReceiveScripts* in `gitblit.properties` or `web.xml`, globally applied to all repositories
|
|---|
| | | 2. post-receive scripts of a Repository definition
|
|---|
| | | 2. post-receive scripts of a Team definition
|
|---|
| | | 3. post-receive scripts of a Repository definition
|
|---|
| | |
|
|---|
| | | ### Destination Addresses
|
|---|
| | |
|
|---|
