Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt

This plugin integrates Atlassian JIRA to Jenkins.


Contents

Table of Contents
maxLevel3

Configuration 

Using JIRA REST API

First, you need to go to Jenkins' system config screen to tell Jenkins where's your JIRA.

This plugin has an optional feature to update JIRA issues with a back pointer to Jenkins build pages. This allows the submitter and watchers to quickly find out which build they need to pick up to get the fix.

If you also want to use this feature, you need to supply a valid user id/password. If you need the comment only to be visible to a certain JIRA group, e.g. Software Development, enter the groupname. 

Warning
titleIncompatible change

Starting from this plugin version 2.0, it is using JIRA REST API to communicate instead of JIRA RPC SOAP which has been deprecated and removed since JIRA v.7.0.
If you have an older JIRA version and still want to use JIRA RPC SOAP, do not upgrade the plugin.

Using JIRA RPC SOAP

...

(deprecated)

NOTE: This applies to plugin version < 2.0 and JIRA version < 7.0.connection type is only supported in plugin v. 1.41 and lower.

JIRA also needs to be configured for Jenkins to remotely login.

...

Referencing JIRA Release version 

To reference Jira JIRA Release versions in your build, you can pull these releases directly from JIRA by adding the JIRA Release Version Parameter

This can be useful for generating release notes, trigerring parameterized build, etc.

Generating Release Notes

You can also generate release notes to be used during your build. These notes can be retrieved from an environment variable. See the Maven Project Plugin for the environment variables found within the POM.

...

The plugin can also move certain issues matching a JQL query to a new release version.

Sample usage of generated Release Notes: Image Added

System properties

Property Name

Functionality Change

-Dhudson.plugins.jira.JiraMailAddressResolver.disabled=true

Use to disable resolving user email from JIRA usernames. Currently there is no option for this in UI.

...

...

Releases

Version 2.1 (?)
  • Bumped Jenkins Core to LTS v. 1.609.2
  • Removed maven plugin dependency
  • Added mailer plugin dependency  
Jira Issues
renderModestatic
columnsKey,Summary,Status
width70%
urlhttps://issues.jenkins-ci.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=labels+%3D+jira-plugin-2.1
Version 2.0.2 (2015-09-15)
Jira Issues
renderModestatic
columnsKey,Summary,Status
width70%
urlhttps://issues.jenkins-ci.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=labels+%3D+jira-plugin-2.0.2
Version 2.0.1 (2015-09-10)
Jira Issues
renderModestatic
columnsKey,Summary,Status
width70%
urlhttps://issues.jenkins-ci.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=labels+%3D+jira-plugin-2.0.1
Version 2.0 (2015-09-02)
Note

Incompatbile change: switch from JIRA RPC SOAP to JIRA REST API communication - the former has been deprecated and dropped since JIRA v.7.0. 

Jira Issues
renderModestatic
columnsKey,Summary,Status
width70%
urlhttps://issues.jenkins-ci.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=labels+%3D+jira-plugin-2.0
Version 1.41 (2015-06-10)
Jira Issues
renderModestatic
columnsKey,Summary,Status
width70%
urlhttps://issues.jenkins-ci.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=labels+%3D+jira-plugin-1.41
Version 1.39 (Oct 6, 2013)
  • Ability only to comment issue without processing of workflow (pull #38)
Version 1.38 (Aug 23, 2013)
  • Post build step to create new JIRA version (pull #30)
Version 1.37 (Jun 21, 2013)
Version 1.35 (Jul 29, 2012)
  • Prevents multiple comments on one issue for matrix builds. (PR #13)

...