| commit | 5e94764b3fbebd4339e0c3ece727da16537f6ee8 | [log] [tgz] |
|---|---|---|
| author | Marco Miller <marco.miller@ericsson.com> | Thu Nov 26 11:35:55 2020 -0500 |
| committer | Marco Miller <marco.miller@ericsson.com> | Thu Nov 26 11:35:55 2020 -0500 |
| tree | 9ceb3eb4b9a0b2880a06d9b6df2b692d9d7d0302 | |
| parent | 32926b606eb9d926666fcfc29000701ce190bd61 [diff] | |
| parent | a369208cbe752f48fa0543eee217ec451f714a0b [diff] |
Merge branch 'stable-3.1' into master * stable-3.1: Upgrade bazlets to latest stable-3.1 to build with 3.1.10 API Change-Id: I7e3ca89828f293232ceb2e045730343f5eb30feb
A simple Gerrit plugin that allows the publishing of certain Gerrit events to a configured Slack Webhook URL. The plugin uses Gerrit's inherited project configuration support so common config options can be set at a higher level and shared by many projects along with project specific config options.
To build the plugin, JDK 1.8 and Bazel are required.
Once installed use bazel to build.
cd ./slack-integration bazel build slack-integration
Once packaged, you can install the ./bazel-bin/slack-integration.jar file into Gerrit.
Installing the Slack Integration Plugin is as simple as copying the resulting JAR file into the Gerrit plugins directory. Assuming you installation of Gerrit is located at /usr/local/gerrit you simply execute the following.
cp ./slack-integration.jar /usr/local/gerrit/plugins
Simple substitute the path to your Gerrit plugins directory as needed. Gerrit automatically loads new plugins and unloads old plugins, no restart is required.
The first thing you need to do is setup an incoming webhook integration in Slack. This is done via my.slack.com - Configure Integrations.
Configuration of the Slack Integration Plugin is done in Gerrit via a project specific config file. This configuration is stored in the project’s project.config file on the refs/meta/config branch of the project.
Common configuration options that can be shared between multiple projects can be placed in the All-Projects config branch, or another project that serves as an inherited base. Config options can then be overridden in the actual project's config branch. For example, you may want to specify a default webhook URL, username and channel then override the channel to be specific to each project.
Editing a project's config
mkdir <project>-config cd <project>-config git init git remote add origin ssh://<admin-user>@<gerrit-host>:29418/<project> git fetch origin refs/meta/config:refs/remotes/origin/meta/config git checkout meta/config
Create the following config block
vi project.config [plugin "slack-integration"] enabled = true webhookurl = https://<web-hook-url> channel = general username = gerrit ignore = "^WIP.*"
Commit and push changes
git commit -a git push origin meta/config:meta/config
The following configuration options are available
enabled – boolean (true/false) When true, enables Slack integration (defaults to false). webhookurl - String The Slack webhook URL to publish to (defaults to an empty string). channel - String The Slack channel to publish to (defaults to "general"). username - String The Slack username to publish as (defaults to "gerrit"). ignore - Pattern A "dotall" enabled regular expression pattern that, when matches against a commit message, will prevent the publishing of patchset created event messages (defaults to an empty string). ignore-unchanged-patch-set - boolean (true/false) Whether a Slack notification about a new patch-set shouldn't be published when code didn't change (defaults to true). ignore-wip-patch-set - boolean (true/false) Whether any Slack notifications regarding a work-in-progress change shouldn't be published (defaults to true). ignore-private-patch-set - boolean (true/false) Whether any Slack notifications regarding a private change shouldn't be published (defaults to true). ignore-comment-author - Pattern A "dotall" enabled regular expression pattern that, when matches against the comment author username, will prevent the publishing of comment added event messages (defaults to an empty string). publish-on-patch-set-created - boolean (true/false) Whether a Slack notification should be published when a new patch set is created. publish-on-change-merged - boolean (true/false) Whether a Slack notification should be published when a change is merged. publish-on-comment-added - boolean (true/false) Whether a Slack notification should be published when a comment is added to a review. publish-on-reviewer-added - boolean (true/false) Whether a Slack notification should be published when a reviewer is added to a review. publish-on-wip-ready - boolean(true/false) Whether a Slack notification should be published when a work-in-progress change is marked ready (defaults to the value for publish-on-patch-set-created). publish-on-private-to-public - boolean(true/false) Whether a Slack notification should be published when a private change is changed to public (defaults to the value for publish-on-patch-set-created).
If a proxy is needed to connect externally to Slack, a proxy server may be configured via Gerrit's main configuration file. The path to this file will vary based on where Gerrit was installed. This example assumes that Gerrit was installed in /usr/local/gerrit.
Edit /usr/local/gerrit/etc/gerrit.config and add the following block.
[plugin "slack-integration"] proxy-host = <hostname or IP address of the proxy server> proxy-port = <port of the proxy server>
The following configuration options are available
proxy-host - String The host of the proxy server, e.g. my.proxy.host (defaults to null). proxy-port - int The port of the proxy server (defaults to 8080) proxy-username - String The username, if needed, to authenticate to the proxy server (defaults to null). proxy-password - String The password, if needed, for the specified username to authenticate to the proxy server, (defaults to null).