This plugin allows to associate Jira issues to Git commits thanks to the Gerrit listener interface.
Git commits are associated to Jira issues 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 : Issues-ids are liked when found on git commit message, no warning are displayed otherwise.
[commentLink "Jira"] match = (\\[[A-Z][A-Z]+-[1-9][0-9]*\\]) html = "<a href=\"http://myjira.com/browse/$1\">$1</a>" association = SUGGESTED
Once a Git commit with a comment link is detected, the Jira issue ID is extracted and a new comment added to the issue, pointing back to the original Git commit.
In order for Gerrit to connect to Jira/SOAP-API url and credentials are required in your gerrit.config / secure.config under the [jira] section.
[jira] url=http://myjira.com username=jirauser passsword=jirapass
Jira credentials and connectivity details are asked and verified during the Gerrit init.
Jira plugin is integrated as a Gerrit init step in order to simplify and guide through the configuration of Jira integration and connectivity check, avoiding bogus settings to prevent Gerrit plugin to start correctly.
Gerrit init example:
*** Jira connectivity *** Jira URL (empty to skip) [http://jira.lmitsoftware.com]: Jira username [admin]: Change admin's password [y/N]? y admin's password : ***** confirm password : ***** Test connectivity to http://jira.lmitsoftware.com [N/?]: y Checking Jira connectivity ... [OK] *** Jira issue-tracking association *** Jira issue-Id 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 Jira to GitWeb will be created, pointing exactly to the Git commit ID containing the Jira issue ID.
Jira plugin is able to automate status transition on the issues based on code-review actions performed on Gerrit; actions are performed on Jira using the username/password provided during Gerrit init. Transition automation is driven by
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 Jira issue when all the condition in the stanza are met.
<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
<code-review-value> : Code-Review flag added on Gerrit with values from -2 to +2
Note: multiple conditions in the action stanza are optional but at least one must be present.
[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: