BuildBug

Description

BuildBug is a Bamboo plugin to create JIRA issues when a build breaks.

Why is this Useful?

I see two main reasons to use this plugin. Firstly, the created JIRA issue provides immediate visibility to the build problem. You can assign the issue to a specific developer once the cause of the failure is known so everyone can see that someone has taken ownership of the problem.

The second reason is less apparent but potentially more beneficial. A build failure is usually associated with some form of waste:

• Someone has to investigate the reason for the failure.
• Someone has to fix the failure.
• Potentially many people are held up from their integration tasks since they can't trust the codebase while the build is broken.

You can use the created JIRA issue (potentially in combination with work logs, custom issue types, work flows, resolutions etc) to record the following information for each build failure:

• How much waste,
• The cause of the waste.

Then you can use JIRA's search/reporting features to identify trends from your build failures, which will hopefully allow you to find and eliminate recurring problems.

For example, you may find a lot of builds failing due to infrastructure issues - this would allow you to better quantify the impact of these problems.

Features

When a Build Breaks, a JIRA Issue is Created.

When a build breaks, a new issue is created. The project, assignee, issue type and priority are configurable.

The following information is included in the issue:

• Why the build failed.
• Test Summary if tests were found.
• List of Authors and associated JIRA issues based on commits.
• A link to the full build log.

BuildBug adds Comments for Subsequent Builds.

The JIRA issue will show the current state of play because BuildBug adds a comment describing the last build result each time a new build completes, until the build is fixed.

Navigate Between Bamboo and JIRA

It's easy to jump back and forth between the JIRA issue and Bamboo build results.

There are links to Bamboo in the JIRA issue description/comments.
With the JIRA Bamboo plugin installed, the "Related Builds" tab shows the builds.
In Bamboo, the JIRA tab shows related JIRA issues including broken builds.

Installation/Setup

Prerequisites

The BuildBug plugin relies on Bamboo JIRA Integration. Please ensure your JIRA integration is working before attempting to install this plugin. One difference is that the JIRA user you supply must have permission to create JIRA issues in the projects you select for each build plan.

Install the Plugin

Install BuildBug as per 6.3 Installing a new Plugin.

Enable BuildBug for a Build Plan

To enable BuildBug, go to the "Post Actions" tab in the configuration for a build plan and scroll down until you see the BuildBug section.

Select the checkbox to enable BuildBug for this build plan.

Select Issue Details

You must select a project, assignee, issue type and priority for the JIRA issue that will be created. The values for the dropdowns come directly from JIRA. Assignee will be validated when you hit save.

There's also an option to use the author from the commit details as the assignee. This will only kick in when a single author is responsible for all the commits contributing to the build. When this is not the case (no commits, or multiple authors) or when the author is not a user in JIRA then the assignee field will still be used.

That's it! Now you get to break the build to test it out.

Possible Future Features

Something that could be useful is changing the state of the JIRA issue. For example, it could be resolved when the build is fixed. I'm not sure how complicated custom workflows will make doing this, so I'll hold off on this one unless people ask for it.

Release Notes

Version 1.0 - codegeist ready!

• BBB-2 Improvement - Include author and jira issues from commit messages in comments

Version 0.9 - release candidate

• New Configuration option - Priority. This controls the priority of the created JIRA issue.
• New Configuration option - Assign to Committer. If enabled, the JIRA issue can be assigned directly to a committer. This will happen if there is a single committer that contributed to the build.

Version 0.4 - track fixing builds

• Comment on the issue and add a change entry when the build is fixed
• Link to the build log in the JIRA comments
• Include test results in the JIRA comments

Version 0.3 - useful for raising visibility of build problems by creating JIRA issues

• Visible/Clickable links between the JIRA issue and Bamboo build.
• Configuration Enhancements
  • Select the project from a dropdown list of projects retrieved from JIRA
  • Validated that assignee is a valid JIRA user
  • Select issue type from a dropdown list of issue types retrieved from JIRA.
  • These configuration features degrade gracefully when JIRA can't be contacted during configuration (don't prevent the build plan from being saved).

Version 0.2 - proof of concept

• Migrate to Bamboo2
• Only one issue per failure period is created.

Version 0.1 - proof of concept

• Can configure whether to enable BuildBug for a build plan, and a Project and Assignee
• Use JIRA configuration details from JIRA plugin

Screenshots

Screenshots
Comments are added to the JIRA issue each subsequent build until it is fixed.	A sample issue created in response to a failed build. A custom issue type named "Broken Build" is used in this instance.	When the build is fixed, an entry is added to the changeset referencing the initial failing build and JIRA issue.
An entry is added to the changeset referencing the created JIRA issue.	Enable on a per build plan basis in Builder Configuration	View the builds related to the created JIRA issue in Bamboo.
The related broken issue is displayed in the JIRA issues tab.	If the JIRA Bamboo Plugin is installed the related build results are shown in the issue 'Related Builds' tab.	Select from the projects, issues types (no subtasks) and priorities available in JIRA. The assignee will be validated against JIRA.
View Configuration.