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
View jira-ext 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:
0.2 Feb 4 2016
- Add Job-DSL support
- Add 'Mentioned in commit message' Issue Strategy
0.1 Jan 11 2016
- Initial release
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:
- The issue key as the first word of the commit message
- The issue key as the first word of the upstream commit message
- Manually specifying an issue
- Looking for it being mentioned somewhere in the commit message
To all of these JIRA issues, you may:
- Add a comment
- Update a field
- Add a label
- Transition a ticket (Start Work, Resolve, etc..)
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:
- Specify issues manually
- Specify issues from upstream commits
- Transitions issues
- Add label to issues
- Update custom fields
- Customize comments on issues
- Perform release notes
- (Deprecated) support for SOAP
- Specify issues from JQL
- Automatically link back to jenkins builds (backpointers)
- 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.
Dan Alvizu firstname.lastname@example.org
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.