JIRA Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID jira Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
2.0 (archives)
Sep 02, 2015
1.560
maven-plugin (version:1.532)
Source Code
Issue Tracking
Pull Requests
Maintainer(s)
GitHub
Open Issues
Pull Requests
Olivier Lamy (id: olamy)
Radek Antoniuk (id: warden)
Usage Installations 2014-Aug 6975
2014-Sep 7178
2014-Oct 7410
2014-Nov 7293
2014-Dec 7210
2015-Jan 7562
2015-Feb 7612
2015-Mar 7955
2015-Apr 7981
2015-May 7947
2015-Jun 8280
2015-Jul 8430

This plugin integrates Atlassian JIRA to Jenkins.

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. 

Incompatible 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.
JIRA RPC SOAP access configuration 

NOTE: This applies to plugin version < 2.0 and JIRA version < 7.0.

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

Go to the general configuration screen and enable remote API calls. Again, this is only needed if you use the abovementioned optional feature, and if you forget to do so, Jenkins will nicely warn you.

With that, JIRA keys in changelogs are now hyperlinked to the corresponding JIRA pages (complete with tooltips!)

Updating JIRA issues with back pointers


To have Jenkins update JIRA issues with back pointers to builds, you also need to configure jobs. I figured you might not always have write access to the JIRA (say you have a Jenkins build for one of the Apache commons project that you depend on), so that's why this is optional.

And the following screen shows how JIRA issue is updated.

By taking advantages of Jenkins' fingerprint feature, when your other projects that depend on this project pick up a build with a fix, those build numbers can also be recorded in JIRA. This is quite handy when a bug is fixed in one of the libraries, yet the submitter wants a fix in a different project. This happens often in my work, where a bug is reported against JAX-WS but the fix is in JAXB.
For curious mind, see this thread for how this works behind the scene.

Referencing JIRA Release version 

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

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.

After your build has run, you can also have the plugin mark a release as resolved. This typically will be a release you specified in your Build Parameters.

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

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.

Related Resources

History

Version 2.1 (?)

Version 2.0 (2015-09-02)

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

Errors were reported by the JIRA trusted connection.

  • BAD_PROTOCOL_VERSION; Unsupported protocol version: {0}. required {1}; ["0","2"]
JIRA Issues (1 issues)
Key Summary Status
JENKINS-18166 Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7 Resolved

Version 1.41 (2015-06-10)

Errors were reported by the JIRA trusted connection.

  • BAD_PROTOCOL_VERSION; Unsupported protocol version: {0}. required {1}; ["0","2"]
JIRA Issues (4 issues)
Key Summary Status
JENKINS-22628 Change comments/description to use String.format() instead. Resolved
JENKINS-21776 Jenkins jira comment text typo Resolved
JENKINS-20528 Unable to link to Jira Resolved
JENKINS-1904 Can't get issue links generated with out user/password Resolved

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)
Version 1.34 (Jun 11, 2012)
  • Fix NPE when Jenkins user does not have access to perform any workflow actions issue #13998
Version 1.33 (Jun 1, 2012)
  • Support workflow steps as build actions and/or post-build notifiers issue #13652
Version 1.32 (May 15, 2012)
  • Option to show archived versions.
Version 1.31 (May 1, 2012)
  • Add JiraIssueMigrator - a post build action that will move issues to a new fixVersion based on a JQL query.
  • Add Additional filtering of issues to be included in the release notes. Defaults to 'status in (Resolved, Closed)'
Version 1.30 (April 25, 2012)
  • Add build parameter that providers a drop-down with JIRA release versions
  • Add a build wrapper that will assemble release notes based on issues in the release version and store it in an environment variable
        # Issue Type
        - [JIRA-123] Issue summary
        - [JIRA-124] Another Issue summary
        # Another Issue Type
        - [JIRA-321] Yet another issue summary
    
  • Add a post-build action that will mark a version as released in JIRA
Version 1.29 (August 25, 2011)
  • issue #10817 Jira-plugin should add the overall build result to the issue's comment
  • Include revisions also for non-subversion plugins; include revisions also if we don't have a repository browser
  • Defined a new parameter type for parameterized builds that allow you to select a JIRA ticket (from the result of a JQL query)
Version 1.28 (Jun 15, 2011)
Version 1.27 (Feb 27, 2011)
  • Updates for Jenkins
Version 1.26 (Jan 14, 2011)
  • (JENKINS-2508) : JIRA plugin not updating JIRA when perforce plugin used.
Version 1.25
  • (JENKINS-6758) : Failed to save system settings with JIRA Plugin.
Version 1.24
  • (JENKINS-6462) : Version 1.355 of Hudson and Jira Plugin 1.21: Images in Jira comments are not showing up.
Version 1.23
  • (JENKINS-6264, JENKINS-6282) fixed : IndexOutOfBoundsException when no issue pattern is configured (default pattern wasn't used)
  • (JENKINS-6381) fixed : configured patterned wasn't used for changelog annotation. Default pattern was always used for that.
  • improved default pattern to not match commit messages with dots in the number part (like 'projectname-1.2.3'). These messages are e.g. used by the Maven release plugin
Version 1.22
  • (JENKINS-6043) : Issue pattern can be configurable
  • (JENKINS-6225) : option to update jira issue whatever the build result is (even if failed)
Version 1.21
Version 1.20
Version 1.19
  • Fix: Prevent carrying forward invalid issue ids forever
Version 1.18
  • Case insensitive matching of JIRA ids also in the 'recent changes' view (JENKINS-4132)
  • fetch missing details for JIRA issues - i.e. completes issue title tooltip in 'recent changes' view (JENKINS-5252)
  • prevent build FAILURE if JIRA site is not available (JENKINS-3046)
Version 1.17
  • Fixed an ArrayIndexOutOfBoundsException when JIRA issues contain '$' in the name.
  • Support underscore in project names (JENKINS-4092)
  • Support digits in project names (JENKINS-729)
  • Case insensitive matching of JIRA ids (JENKINS-4132)
  • Don't strip JIRA id from posted comment
  • German translation
Version 1.15 (2008/08/22)
  • Update JIRA if the build is UNSTABLE or better.  Previously only updated if the build was stable.
  • Include relevant SCM comment in the JIRA comment which should make JIRA ticket history more meaningful.
Version 1.13 (2008/08/05)
  • Fixed a performance issue in a large enterprise deployment of JIRA (issue #1703)
Version 1.12
  • A typo in the commit message shouldn't break builds (issue #1593)
  • Postpone JIRA updates until a successful build is obtained (issue #506)
Version 1.11
  • Added more logging and debug flag to examine issues that people are reporting (report)
Version 1.10
Version 1.9
Version 1.8
Version 1.7
  • Fixed NPE when username/password is not set (issue #828)
Version 1.6
  • Relaxed the JIRA project key regexp a little bit to allow numbers (issue #729)
Version 1.5
  • Issue hyperlinking is now smart enough not to be confused by strings that look like JIRA issue that actually aren't.
Version 1.4
  • Fixed a bug that prevented tooltips for JIRA issues from being displayed issue #694

Labels

Edit
plugin-maven plugin-maven Delete
plugin-external plugin-external Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment