Atlassian Bamboo enables development teams to adopt continuous integration (CI) in minutes, providing fast feedback about code changes so bugs don't pile up. As teams ramp up their CI effort, Bamboo can be scaled with remote agents located on-premise or in the Amazon EC2 cloud.
|Tags||Software Development Build Tools|
|Operating Systems||Linux Windows Mac OS X|
Release Notes: This release adds new integration points for JIRA, Stash, and HipChat, as well as other features that help get your team together.
Release Notes: This release adds Plan Branches which work for both DVCS and centralized version control environments. Advanced support for DVCS automatically detects new branches as they are created, tests the changes, and can merge the branches into mainline development. For VCS, developers can easily add a Plan Branch to the Plan, manually. The new Test Quarantine feature allows system administrators to isolate a broken test so it can be re-visited at a later time and not affect the outcome of the build. UI changes are also part of the release.
Release Notes: This release introduces support for Git submodules. Also, users now have the ability to share repository configurations, making it easier to admin and maintain plans. Further improvements include support for Windows in Amazon EC2 (elastic agents) and new email notifications.
Release Notes: This release introduces Multiple Repository support: monitor and checkout code from multiple repositories including Subversion, Git, Mercurial, CVS, and Perforce. This allows you to build and include externally developed open source software as part of your project, or larger projects that consist of multiple modules located in different repositories. It also adds automatic upgrades of remote agents: agents now start up faster, auto-update, and reload plugins. Also included is Java 7 support, support for multiple user aliases, a commit centric view of your build activity, and much more.
Release Notes: This release introduces improved integration between Bamboo and JIRA to automate the release management process (down to one click). Manual Stages allow you to interrupt/halt/suspend automatic build execution at a specific Stage in the build plan. For Plan execution to continue, a user must manually trigger the Stage. Also, you can now re-run failed Jobs without having to re-run the entire Plan once you've resolved the problems.