Summary

A plugin for Jenkins CI to update JIRA tickets in an extensible way: both what to update and how to up date are exposed as Extension Points

{jenkins-plugin-info:pluginId=jira-ext|jiraComponent=jira-ext-plugin}

Release Notes

0.8 March 23 2019

0.7 June 15 2017

0.6.1 December 15 2016

0.5 May 24 2016

0.4.1 March 4 2016

0.4 March 3 2016

0.3 (Failed release - eaten by INFRA-588)

0.2 Feb 4 2016

0.1 Jan 11 2016

Overview

A plugin for Jenkins CI to update JIRA tickets in an extensible way: both what to update and how to update are exposed as ExtensionPoints.

Out of the box, you may discover issues by:

To all of these JIRA issues, you may:

Comparison to jira-plugin

The jira-ext plugin is meant to be extensible in ways that the jira-plugin is not. Both Jenkins and JIRA are used as part of an organizations workflow, and as such are highly customizable. The jira-ext plugin continues this philosophy by making the actions (and when to perform those actions) also customizable for your organization.

In terms of specific features:

jira-ext plugin:

  1. Specify issues manually
  2. Specify issues from upstream commits
  3. Transitions issues
  4. Add label to issues
  5. Update custom fields
  6. Customize comments on issues

jira-plugin:

  1. Perform release notes
  2. (Deprecated) support for SOAP
  3. Specify issues from JQL
  4. Automatically link back to jenkins builds (backpointers)
  5. Link JIRA issues in the Jenkins UI

Extending the plugin

The jira-ext plugin is built with extension in mind. Both how to discover issues and what action to take are customizable. They are implemented as ExtensionPoint, meaning your plugin (or a custom plugin) can contribute its own ticket discovery strategies or operations based on logic specific to your installation or environment.

For example, a code review build could provide a link to the code review server in the JIRA issue as a custom field, or as a comment.

Or another example, a production release build could update tickets based on differences between tags, to keep track of what was deployed last.

If you want to add an operation which should be part of any JIRA install, please open a pull request.

Add a custom 'Discover Issues By' option

You may update what tickets to update using an IssueStrategyExtension and IssueStrategyExtensionDescriptor. SeeSingleTicketStrategy for an example.

Add a custom JIRA operation

You may add your own operations using a JiraOperationExtension and JiraOperationExtensionDescriptor. SeeAddComment for an example.

FAQ:

How does the plugin work?

The jira-ext plugin is a build step in Jenkins - it updates JIRA tickets through a REST API:

the 'ext' in the JIRA-ext plugin stands for 'extensible' - both of those bullet points can be extended by writing your own plugin. Jenkins wiki has docs on that:
https://wiki.jenkins-ci.org/display/JENKINS/Extend+Jenkins

I have a question, how should I ask it?

The jira-ext plugin is an open source project, and questions should be transparent to benefit the community. In order of preference, please:

  1. Open a Pull Request in github
  2. Look for a JIRA issue or create a new one if one does not exist
  3. Ask on the jenkins user list

If those do not work or get a reply within a week, please contact the author directly.

Authors

Dan Alvizu alvizu@gmail.com

License

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License athttp://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.