Atlassian Bamboo

Atlassian Bamboo – Continuous Integration

Atlassian Bamboo is one of the leading software solutions for CI (Continuous Integration) and build servers in software development. This platform-independent continuous integration software is also used for software deployment and release management. Bamboo enables automated builds, tests and releases to be carried out using workflows. This means that all programming languages can be integrated and subsequently tested. Furthermore, as with all Atlassian products, you benefit from easy integration options with other in-house software such as Jira, Bitbucket, Hipchat or Fisheye.

Who does Atlassian Bamboo help?

Request a no-obligation consultation

Benefit from seamless integration with Atlassian products (Jira, Confluence, Bitbucket, etc.), the user and admin interfaces, and parallel batch tests. Discover many more benefits:

Unified code base

Automated code generation

Early fault-finding

Automated testing

Automated and continuous testing of the current code

Accurate recording of changes

An insight into the stages of development

Specific process adjustments

We are your trusted Atlassian Platinum Partner

As an Atlassian Platinum Solution Partner and Cloud Migration Specialised Partner for EMEA, you’ll benefit from our extensive experience and best practices gained from numerous client projects. Put your trust in Communardo to set your projects on the path to success. We provide all services under one roof.

As an Atlassian Partner, we’re here to support you. If you have any questions or need assistance, please feel free to contact us.

You would like some advice

How does Atlassian Bamboo work?

Atlassian Bamboo is the central management server that plans and coordinates all tasks. The software itself, in turn, features interfaces for many different types of tasks. Furthermore, as with all Atlassian products, you can draw on a large number of plug-ins. These make day-to-day use of Bamboo much easier. These plug-ins also serve as a starting point in the source repository.

In the source repository, source code files and similar items are stored in a project archive. These are ‘checked out’ and downloaded to the programmer’s computer when requested. Once edited, these files are checked back in and the changes are logged. This version control system is used, for example, to reconstruct previous states.

Furthermore, these plug-ins are available across a wide range of systems. Once the input has been retrieved, Bamboo starts the build. This can be done, for example, by calling MSBuild to build your Visual Studio solution. As soon as your solution or project is complete, ‘artifacts’ become available to you. (These include, for example, build results, such as executable applications or configuration files.) With these ‘artifacts’, you can, for example, run an installation builder on them, create an MSI, or install them on a test server for verification. You can also pack them into a ZIP file, which you can then copy anywhere.

In addition, Bamboo offers a front-end that can be configured according to requirements or user preferences. This also serves as an overview of the respective status of the builds, enabling you to monitor the project on an ongoing basis.

You would like some advice

How is the Bamboo workflow organised?

Atlassian Bamboo uses the concept of a ‘project’ comprising a ‘plan’, ‘stage’, ‘job’ and ‘task’ to configure and organise the actions within the workflow. We explain this concept in more detail below:

Project

A project presents the entire campaign in reports and provides links to other applications. A project contains one or more plans. Furthermore, permissions can be set up within projects for all the plans it contains.

Plan

Specifies the default repository and describes how the build is triggered. The triggering dependencies between plans from other projects are also specified here. Notifications regarding build results are also contained within the plan. As with the ‘Project’, permissions for viewing and configuring the plan and its jobs can be set here. Plans normally consist of a single ‘stage’, although these may be displayed across multiple stages for grouping purposes.

Stage

A stage consists of a single ‘job’,which is processed in parallel on multiple agents (where available). For the Bamboo CI server to process the plan, all jobs must be successfully completed. Furthermore, ‘artifacts’ are generated here, which can then be made available.

Job

Jobs process either individual tasks or several consecutive tasks, which are executed one after the other on the same agent in a specified order. In addition, the requirements of the Bamboo CI server are collected here so that they can be matched against the agents’ capabilities. Jobs also contain the ‘artifacts’ from the ‘stage’, which are defined here and generated by the build. Finally, all the labels used to tag the build result or the build ‘artifacts’ are specified.

Task

Tasks are small, discrete units of work, such as ‘source code verification’, executing a Maven target, or scripting/parsing test results. These are executed sequentially within a job in a Bamboo working directory.