This is the documentation for Bamboo 5.7. View this page for the

Unknown macro: {spacejump}

of Bamboo, or visit the latest Bamboo documentation.

Overview

When Bamboo is integrated with a JIRA application, it can pass important development information back to a JIRA application. Currently Bamboo can pass information relating to:

  • Build results
  • Deployment statuses

The information is collated within the Development Panel. This panel summarizes the status of all work related to an issue, and can assist in identifying where an issue's build is failing, and where it has been deployed.

Example
  • If you are working on issue BAM-12443, then you can see if it has been deployed to a development server yet 
  • A QA can also check to see if it's on their QA server and ready for testing 
  • A manager can see if a bug has made it to production.

Linking a JIRA application and Bamboo has the benefit of improved information exchange during your development process.

See Integrating Bamboo with JIRA applications for information about permissions and configuration.

Related pages:

On this page:

 

The development panel

The Development panel provides an 'at-a-glance' development information resource, and is visible to anyone with the "View development tools" project permission. The panel replaces the Builds tab and Issue deployment panel, and summarizes an assortment of development data passed to a JIRA application from Bamboo and other Atlassian products. Examples include:

  • Feature branch creation from JIRA applications
  • Viewing repository branches in Bitbucket or Stash
  • Viewing commits and pull requests to Git repositories managed by Bitbucket or Stash
  • Viewing commits, branches and reviews in FishEye/Crucible
  • Viewing build result and deployment information in Bamboo

 

Viewing build result information

The Development panel shows the status of the latest Bamboo builds related to your linked issue. Using simple status icons builds are reported as:

  all the different builds (for example, unit tests, functional tests, deploy to staging) succeeded
  at least one run failed for any build by any linked instance of Bamboo. 

A build is automatically linked to an issue if one of the build's commits includes the issue key in its commit message. The issue key must be included in the commit to activate this feature. 

Clicking the associated builds link reveals additional build details including the name of the plan branch and how many tests passed or failed:

Viewing deployment information

A deployment to an environment, such as Production or testing, is linked to an issue if a commit associated with the deploy contains the issue key in its commit message. The Development panel details the environments that associated Bamboo builds have been deployed to.

The issue key must be included in the commit to activate this feature.

Clicking the Deployed link reveals deployment details including the deployment status, release date, and click through to view a particular deployment:

Note the 'Deployment Panel' is no longer displayed on an issue when the 'Development Panel' is available.

  • No labels

 

 

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.