This plugin allows to associate Bugzilla bugs to Git commits thanks to the Gerrit listener interface.
Git commits are associated to Bugzilla bugs reusing the existing Gerrit [commitLink configuration]i1 to extract the issue ID from commit comments.
Additionally you need to specify the enforcement policy for git commits with regards to issue-tracker associations; the following values are supported:
MANDATORY : One or more issue-ids are required in the git commit message, otherwise the git push will be rejected.
SUGGESTED : Whenever git commit message does not contain one or more issue-ids, a warning message is displayed as a suggestion on the client.
OPTIONAL : Bug-ids are liked when found on git commit message, no warning are displayed otherwise.
Example:
[commentLink "bugzilla"] match = \\([Bb][Uu][Gg][ ]*([1-9][0-9]*)\\) html = "<a href=\"http://mybugzilla.org/show_bug.cgi?id=$1\">(bug $1)</a>" association = SUGGESTED
Once a Git commit with a comment link is detected, the Bugzilla bug ID is extracted and a new comment added to the issue, pointing back to the original Git commit.
Note that the plugin relies on $1 holding the numeric id, so we cannot have match group 1 spanning over the whole “(Bug 4711)”.
Be sure to label the commentLink “bugzilla” with lowercase “b” to match the config section's name below.
In order for Gerrit to connect to Bugzilla/XML-RPC url and credentials are required in your gerrit.config / secure.config under the [bugzilla] section.
Example:
[bugzilla] url=http://mybugzilla.org username=bzuser password=bzpass
Bugzilla credentials and connectivity details are asked and verified during the Gerrit init.
Bugzilla plugin is integrated as a Gerrit init step in order to simplify and guide through the configuration of Bugzilla integration and connectivity check, avoiding bogus settings to prevent Gerrit plugin to start correctly.
Gerrit init example:
*** Bugzilla connectivity
***
Bugzilla URL (empty to skip) [http://mybugzilla.org]:
Bugzilla username [admin]:
Change admin's password [y/N]? y
admin's password : *****
confirm password : *****
Test connectivity to http://mybugzilla.org [N/?]: y
Checking Bugzilla connectivity ... [OK]
*** Bugzilla issue-tracking association
***
Bugzilla bug number regex [([A-Z]+-[0-9]+)]:
Issue-id enforced in commit message [MANDATORY/?]: ?
Supported options are:
mandatory
suggested
optional
Issue-id enforced in commit message [MANDATORY/?]: suggested
When Gerrit gitweb is configured, an additional direct link from Bugzilla to GitWeb will be created, pointing exactly to the Git commit ID containing the Bugzilla bug ID.
Bugzilla plugin is able to automate status transition on the issues based on code-review actions performed on Gerrit; actions are performed on Bugzilla using the username/password provided during Gerrit init.
When using this possibility, the plugin assumes that gerrit.canonicalWebUrl is set. If it is not, the plugin will throw exceptions.
Transition automation is driven by $GERRIT_SITE/issue-state-transition.config file.
Syntax of the status transition configuration file is the following:
[action "<issue-status-action>"] change=<change-action> verified=<verified-value> code-review=<code-review-value>
<issue-status-action> : Action to perform on Bugzila issue when all the condition in the stanza are met. can be any of: status STATUS change the associated bug‘s status to STATUS, where STATUS can be any of the values your bugzilla configuration allows as status. Be aware, that changing a bug from any status for open bugs to a status for closed bugs will not work, as the resolution would be missing. resolution RESOLUTION change the associated bug’s resolution to RESOLUTION, where RESOLUTION can be any of the values your bugzilla configuration allows as resolution. Setting the resolution has only an effect if the associated bug is in a closed state.
<change-action> : Action performed on Gerrit change-id, possible values are: created, commented, merged, abandoned, restored
<verified-value> : Verified flag added on Gerrit with values from -1 to +1 For positive values, you must not omit a leading +.
<code-review-value> : Code-Review flag added on Gerrit with values from -2 to +2 For positive values, you must not omit a leading +.
Note: multiple conditions in the action stanza are optional but at least one must be present.
Example:
[action "Start Progress"] change=created [action "Resolve Issue"] verified=+1 code-review=+2 [action "Close Issue"] change=merged [action "Stop Progress"] change=abandoned
The above example defines four status transition on Jira, based on the following conditions: