Bamboo 4.2 release notes
13th August 2012
With dependencies, build strategies and notifications for Plan Branches in Bamboo 4.2, working with branches in Git, Mercurial, Subversion and other version control systems has never been easier. Updated Subversion support now detects new branches automatically, which means that you can build and test all your branches without touching a thing.
Notifications for your branches just got more flexible. Inherit from your plan's notification settings, send notifications only to committers or your favorite branches, or send no notifications at all.
Want to run your branch build at 2am? Plan branches now have their own build strategy settings just like normal plans.
Dependencies for branches are now here! If both the triggering plan and the receiving plan have a plan branch with the same name, the triggering plan can trigger a branch build of a child.
Defaults for automatic branching
Configure your automatic branch detection so that new branches merge back to master when the build completes, and set default notification preferences for your new branches so the right people on your team get notified of build failures.
Better handling when branches are deleted
When a branch is deleted or is marked as closed the plan branch is automatically disabled, reducing the load on Bamboo and making finished feature branches easy to identify in the user interface.
Configure a default merging strategy for automatically created branches
Automatically link your issue to feature branches
If you create a new branch in Git, Mercurial or Subversion that contains a JIRA issue key, Bamboo will automatically link the branch to the JIRA issue . Now you can track all the related builds for your branch from the JIRA ticket and see their latest status.
Get to artifacts from your JIRA issue
Back by popular demand – download Bamboo artifacts directly from the Builds tab of your JIRA ticket.
Link multiple issues to a build at once
To save time when manually linking many JIRA issues to a build, you can put multiple comma-separated issue keys in the link issues field.
If your feature branch contains a JIRA issue key Bamboo will link it back to JIRA.
Just like Bitbucket itself, the Bamboo Bitbucket connector has support for Git repositories. We've also changed the way that Bamboo interacts with the Bitbucket service so that using the connector feels smoother and snappier.
Better Windows support
Problems with stuck or hung Bamboo builds when using native Git and SSH repositories on Windows have been obliterated.
Native Git will rock your world
Native Git support makes all Git operations super quick just like they are on your local machine. If you have Git installed on your machine, Bamboo will do its best to upgrade from its built-in Git to the new native Git.
Thought we would forget GitHub? We've taken all the user experience improvements from the Bitbucket connector and brought them to GitHub users. We love you too.
A number of problems that prevented Gatekeeper with Git from behaving reliably have been fixed. If you are using automatic merging and Git, this update is a great improvement.
The Bitbucket connector now supports Git repositories
Automatically detect new branches
Bamboo automatically detects new branches as they are created in your repository and sets up builds for them using plan branches.
Works with the new toys we introduced with plan branches
Build strategies, dependencies and notifications for branches are not just for Git – they work for Subversion branches too.
Support for Subversion 1.7
Updates to our Subversion support mean it is now possible to use the Subversion 1.7 working space format. More...
Automatically detect and build new branches from Subversion repositories
New results screen
The new results summary screen displays the information you need to diagnose build failures, including comments, test failures and configuration change warnings, right at the top of the page. Since you need to respond to failures fast, operations such as comments are done inline without page refreshes.
Re-run failed jobs from any results screen
Re-running failed jobs is easier now that you can re-run jobs from any results screen, not just from the plan result.
Need to make a quick configuration change? Press E on any build summary or result page and be automatically taken to the configuration settings for Plans, Jobs and Plan Branches. Quickly organize your plans and results by pressing L to add labels.
The user experience of the result summary has been overhauled to display relevant information first and avoid page refreshes where possible
Don't wait – the page load times have been improved right across the user interface, including saving the configuration of plan branches.
Mercurial commit isolation
Just as for Subversion and Git, Mercurial repositories now support commit isolation, so you can test each individual commit to a repository.
Database pool size increase
Thanks to the feedback from customers with large Bamboo instances, the default database connection pool size has been increased from 25 to 100 connections to improve throughput. Existing customers will need to change their database pool configuration to make use of this recommendation.