Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 47 Next »

Plugin Information

View JIRA on the plugin site for more information.

Older versions of this plugin may not be safe to use. Please review the following warnings before using an older version:

This plugin integrates Atlassian JIRA to Hudson.First, you need to go to Hudson's system config screen to tell Hudson where's your JIRA. This plugin has an optional feature to update JIRA issues with a back pointer to Hudson 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.
JIRA also needs to be configured for Hudson 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, Hudson will nicely warn you.

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

To have Hudson 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 Hudson 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 Hudson's fingerprint feature, when your other projects that depend on this project picks up a build with a fix, those build numbers can be also recorded to 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.

Related Resources

  • Check also the Marvelution Jira Hudson Integration which provides a two-way solution Hudson->JIRA and JIRA->Hudson

History

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 (JENKINS-1703)
Version 1.12
  • A typo in the commit message shouldn't break builds (JENKINS-1593)
  • Postpone JIRA updates until a successful build is obtained (JENKINS-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 (JENKINS-828)
Version 1.6
  • Relaxed the JIRA project key regexp a little bit to allow numbers (JENKINS-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 JENKINS-694
  • No labels