Channels ▼


Atlassian Shoots New Test/Plan Branches Into Bamboo 4

Collaboration software company Atlassian has cultivated new functionality options into Bamboo 4, the newest release of its continuous integration and delivery server. The new iteration includes options to automatically test code on development branches before merging with the main code line.

"Every version control system, whether it's centralized or distributed, brings advantages to the developer but also workflow challenges. Bamboo 4 bakes in the best practices in workflow to make the continuous integration process more streamlined without having to know all the details," said Jean-Michel Lemieux, vice president of engineering at Atlassian. "Bamboo gives software developers the best of both worlds — feature branching and continuous integration — and works the way developers work."

The new release also includes user interface improvements, which have been specifically built with a view to allowing developers to provide rapid feedback on build failures by navigating builds faster. Atlassian also wants programmers to be able to browse plans and identify build failures more quickly.

It provides automatic plan branching and merging for distributed version control systems (DVCS) like Git and Mercurial as well as push-button plan branching for traditional version control systems (VCS), such as Subversion, Perforce, and CVS. Developers can reuse the same build configuration across branches. These features have been incorporated so developers can integrate changes irrespective of which branch contains the new code.

NOTE: DVCS encourages a practice called branching, which makes a copy of the source code at a certain point in time and allows developers to briefly work in isolation on their branch before merging their changes back into mainline development.

Bamboo's support for DVCS detects new branches as they are created, tests the changes, and can merge the branches into mainline development.

Bamboo also now comes with a "Test Quarantine" feature. A process for system administrators to isolate a broken test so that it can be revisited at a later time and not affect the outcome of the build. Once quarantined tests are revamped, developers can reintroduce them. Bamboo 4 provides the count of Quarantined Tests in every build as a reminder to reincorporate them.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags


<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags


<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

