Atlassian Software Systems is proud to announce the release of Bamboo 1.2. This release contains:
- Permissions (global and plan-based)
- External database support
- Perforce triggering support
- Scheduled backups
- New Bundled NAnt plugin
- Lots of minor features and bug fixes
Bamboo 1.2 can be downloaded here, and is of course free to all customers who purchased their Bamboo licence or maintenance after July 9, 2006.
When upgrading, please refer to the Bamboo 1.2 Upgrade Guide.
Permissions (global and plan-based)
Different organisations, and different projects, have different security requirements. Some information can be made public, while sensitive information may need to be confined to a particular group of people.
Bamboo 1.2 gives you the ability to set security on individual build plans, as well as on your entire Bamboo system:
- Plan permissions allow your chosen users to perform a particular operation in relation to a particular build plan (e.g. view its build results).
- Global permissions allow your chosen users to perform a particular operation in relation to Bamboo as a whole.
External database support
Bamboo ships with a built-in HSQL database, which is well suited to evaluation purposes. When deploying Bamboo in production, however, you will probably prefer to connect Bamboo to an enterprise database of your choice.
Perforce triggering support
We are pleased to announce that Bamboo builds can now be triggered by Perforce repositories (previously only Subversion and CVS repositories were supported).
You can now schedule your Bamboo data exports to occur automatically at a convenient time:
New Bundled NAnt plugin
Want to build your .Net projects on Bamboo? Now you can, with the NAnt plugin, which comes bundled by default with Bamboo 1.2.
On the topic of plugins, have you checked out the Bamboo plugins, home to a whole host of cool Bamboo plugins?
Other updates and bug fixes
On top of these features, Bamboo 1.2 also includes a host of minor new features, improvements and bug fixes:
Unable to locate JIRA server for this macro. It may be due to Application Link configuration.