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

Unknown macro: {spacejump}

of Bamboo, or visit the latest Bamboo documentation.

When you integrate Bamboo with Atlassian's Stash Git repository management solution, commit, branch, build and deployment information is shared for users of both applications.

On this page:

Benefits of integration

Integration between Bamboo (versions 5.6 and later) and Stash (versions 3.1 and later) only requires:

  • an application link to be configured between them, and 
  • a Stash repository to be specified in a Bamboo plan. 

Bamboo is then automatically configured to respond to repository events published by Stash, and to notify Stash about build results – you don't have to configure repository polling for new commits anymore in Bamboo, or set up dedicated web hooks in your Stash instance. 

Stash tells Bamboo when to build

  • When a developer pushes to a repository the build is automatically started. 

Stash tells Bamboo when to update plan branches to match changes in repository branches

  • When a developer pushes a new branch to a repository a branch plan is automatically created.
  • When a developer deletes a branch in a repository, the branch plan is automatically deleted or disabled. 

Stash commits are displayed in the relevant Bamboo builds

  • In Bamboo, you can view all of the commits involved in the build, allowing you to accurately track changes:

     
  • Simply click on a changeset to go to Stash, where you can see the commit diff for all of the files that are part of the build.

Bamboo notifies Stash automatically about build results

  • Build notifications are automatically enabled when you link a build plan to a Stash repository.
  • Notifications are sent to all linked Stash servers.
  • You see the build results status for a commit when viewing any commit or pull request in Stash, so you can easily check the build status of a branch when deciding whether to merge changes:
  • Click a build status icon in Stash to see further details:


Stash displays the overall status of the build results. The status is 'passed' if all the different builds (for example, unit tests, functional tests, deploy to staging) have succeeded, and 'failed' if at least one run failed for any of those.

For example, when viewing the Commits tab for a Stash project, you will see icons that indicate the status of the latest build results. The red 'fail' icon is displayed if there is at least one failed build run for the commit.

Note that the legacy Stash notification type is deprecated – it is still available in Bamboo 5.6 but will be removed in Bamboo 5.7.

Configuration

There are just a few simple configuration steps to get the integrations described above with Bamboo (versions 5.6 and later) and 
Stash (versions 3.1 and later):

Bamboo-to-Stash

You only need to do this once for each pair of Stash and Bamboo instances.

See Linking to another application.

Once linked, all the Stash repositories are available to your plans in Bamboo.

 

2. Choose the Stash repository for the Bamboo plan

Create a build plan (if necessary) and specify the repository in the plan (or job) configuration.

See Stash for more information about using Stash source repositories in Bamboo. 

 

3. Build!

  • No labels

 

 

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