Bamboo 3.2 Now Available
Automate your complete release process down to one-click, add manual Stages to your deployment process, and re-run failed Stages with the new Bamboo 3.2.
What’s New in Bamboo 3.2
1. Release Management
The dream scenario with any release process is to automate all of your release activities down to the click of a single button. Bamboo 3.2 and the new Release Management plugin for Jira aims to do just that – one-click release management.
- Prevent mistakes from being made as part of a long, manual release process
- Remove the barrier to release
- Speed up the release – the more often you do it, the faster you will make it
- Manage all your releases from a centralized and controlled location
- Use the same streamlined, automated process every time you release
Release in Jira, build in Bamboo! Create a release pipeline in Bamboo to automate your release process: use Stages, Jobs and Tasks to build, run tests, generate release artifacts, publish and deploy your release. Then initiate your release activity or event with one-click directly from Jira when you’re ready.
Run a release build in Bamboo from the Jira Versions tab without leaving Jira.
When releasing a version in Jira you will have the option to run Bamboo builds.
If the build is successful the version will be released in Jira.
Automate the steps that traditionally are performed to release an application:
- Building and testing
- Tag the releases, assign a version
- Create and populate the release branch
- Deploy the release to a a deployment server or production environment
- Release the new version in Jira, move the unresolved issues to the next release
- Release or activate the new version in Production
Bamboo ships with a number of Tasks to build and deploy including Tasks to tag or branch a repository.
For JIRA-Bamboo users the latest release of the Bamboo-Jira plugin is now compatible with Jira 4.3 and provides this release management functionality.
2. Manual Stages
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.
The default behavior of any Build Plan in Bamboo is to go to the next Stage upon successful completion of the current stage. Depending on your needs you may need to introduce a manual checkpoint into your build plan before going on to the next Stage:
- Use a manual stage for deployment to give your QA team a chance to perform a few manual tests before your software goes into production
- In a release pipeline, you may want to separate your ‘publish’ step from your ‘install’ step and install only after backups or clean shutdowns have been confirmed
- Introduce a ‘quality’ gate, between build and deploy stages, to allow members of your team to approve and promote a particular build
- Any other step that’s difficult to automate or that requires special attention
3. Re-run Failed Stages
4. Filter Bamboo Dashboard by Labels
Hint: When viewing a Plan use the keyboard shortcut “l” to bring up the label dialog for the Plan. When viewing the Bamboo Dashboard press “l” to filter the
dashboard by label.
And More…
- Improved Jira integration – delegate user management to Jira, easier application linking
- EC2 improvements
This release has over 50 new features and improvements implemented. Check out the full release notes for more details.
Ready to download
Download Bamboo 3.2 now to get started with a 30-day FREE trial or upgrade your current instance.
