This page last changed on May 08, 2007 by mark@atlassian.com.

The Atlassian Bamboo team is proud to announce the release of Bamboo 1.1! This release contains a whole host of new features targetted to make your build plans even more powerful and flexible.

Want to see Bamboo 1.1 in action? Check out our live opensource instance.

Advanced Notifications

In this release, we have extended Bamboo notifications framework to provide more flexibility, allowing you to select the how, who and when of notifications.

Notification Rules

Rather than having static fields for emails/IM recipients, Bamboo now allow you to define your own notifications for your build plans as a set of rules, giving you greater granularity in controlling exactly which recipient gets notified and when.

Notification Triggers

In release 1.1, we introduce notification triggers, defining exactly when you would like a notification to be sent by Bamboo. By default, you can select a notification to be sent on "all builds completion", "after X failed builds" or "failed builds and first successful build". Want more customized triggers? You can now write your own as a notification condition plugin.

Notification Preferences

Different users prefer to get notified in different ways. Bamboo now lets you control that, via the new user notification preferences.

Dynamic recipients

Only want to receive a notification when you have committed against the build? Want to opt-in to receive notifications on the build plan that you are keeping an eye on? Bamboo 1.1 introduces two new dynamic recipient roles: committers (those users who have committed to the plan triggering the particular build to execute) and watchers (those users who have marked the build plan as their favourite), which allow you to do just that!

Build Metadata

Every build process is different, and each build will have its own information that you may want to keep track of and use on top of the information that Bamboo stores about your build. This is particularly the case if you run custom plugins in your build process.

Pass them to your build

One way to use your build metatdata is to pass it along to your builder as a property or target. To do this, you simply specify your variables in your target (or goal) field in your builder configuration. During build execution, the variables will be substituted with the actual values from your build metadata.

Global Variables

Bamboo 1.1 also allows you the option to specify variables globally. When a build begins, the global variables will be populated to the build's metadata. This is a handy option for you to control many plans in one go.

View your metadata

Use the "Metadata" tab to keep track of all of your build's metadata.

File Trigger Inclusions/Exclusions

In this release, we also introduce the file trigger inclusion/exclusion filter. Instead of listening and picking up all changes from a repository, you can now use regex patterns to define those files which you do (or don't) want to trigger builds.

More pluggability

In release 1.1, we have added more plugin points to make Bamboo even more extensable than before. On top of the notification condition plugin point, we have also added pre-build action plugins, as well as repository plugins.

  • Repository Plugins Not using SVN, CVS, or Perforce? You can now write a plugin to integrate with your very own source control.
  • Pre-build Plugins Similar to the post-build action plugin, the pre-build action plugin will allow you to perform any custom task you may wish. The only difference is, of course, that it occurs before the build execution begins.

Improved Maven 2 error log parsing

Bamboo now intelligently parses the Maven 2 error log for possible errors in the build errors log, giving you a better view of what really went wrong in your build summary.

LDAP and external user management support

In release 1.1, we have improved our user management capability to support externally sourced users and groups, including LDAP, and Crowd

Performance of Dashboard

With this release, we have also made significant performance improvements to the dashboard, which should see its load times reduce dramatically.

Other updates and bug fixes

On top of these features, we have also made a whole host of bug fixes, with over x bugs fixed since release 1.0.5.

Atlassian JIRA (43 issues)
Key Summary Pr Status
BAM-940 Make Repository pluggable Critical ResolvedResolved
BAM-1189 Add global variables to be used in plans Major ResolvedResolved
BAM-1183 Tool tip in the dashboard for the plans. Major ResolvedResolved
BAM-1163 Dashboard very slow Major ResolvedResolved
BAM-1134 "operation not permitted" clicking Completed Builds tab Major ResolvedResolved
BAM-1117 Ant builder checks last 5 lines for BUILD SUCCESSFUL Major ResolvedResolved
BAM-1115 Artifact URL fails to escape invalid characters Major ResolvedResolved
BAM-1090 Allow pluggable pre-build actions Major ResolvedResolved
BAM-1088 Hide User Info From Non-Admins Major ResolvedResolved
BAM-1080 Lock obtain timed out error Major ResolvedResolved
BAM-1073 No way to pass proxy information down to Ant Major ResolvedResolved
BAM-1059 Implementation of new style of Notifications Major ResolvedResolved
BAM-1058 Error viewing Build: Expression failingSinceBuild.buildResultsSummary is undefined Major ResolvedResolved
BAM-1053 ANT_HOME is used for ant Major ResolvedResolved
BAM-1032 NullPointerException accessing RSS feed Major ResolvedResolved
BAM-1029 LDAP integration Major ResolvedResolved
BAM-1020 Inconsistent Test Results between builds Major ResolvedResolved
BAM-1016 Allow include/exclude patterns for triggering build Major ResolvedResolved
BAM-1011 bamboo.home is not a valid environment variable Major ResolvedResolved
BAM-1010 Error summarry should parse logs in Maven 2 builds Major ResolvedResolved
BAM-996 FreeMarker template error in Completed Build Results screen Major ResolvedResolved
BAM-952 Bamboo uses older m2 version even when maven 2.0.5 builder configured for the plan Major ResolvedResolved
BAM-950 Out of memory error while processing Clover 2.0a4 results Major ResolvedResolved
BAM-942 Upgrade jfreechart version due to concurrency bug Major ResolvedResolved
BAM-938 Editing LDAP users in Bamboo Major ResolvedResolved
BAM-934 OutOfMemory while checking a build result Major ResolvedResolved
BAM-847 Remote API for manual checkout and build. Major ResolvedResolved
BAM-819 'Important Files and Directories' Major ClosedClosed
BAM-787 add screenshots (when Clover data is available) Major ResolvedResolved
BAM-767 We able to add custom project specific Build Telemetry data Major ResolvedResolved
BAM-729 make terminolody consistent ("build" vs. "plan") Major ResolvedResolved
BAM-641 Ability to ignore file patterns for updates Major ResolvedResolved
BAM-633 Add Recent Activity tab for the dashboard Major ResolvedResolved
BAM-574 The interface used to provide a view of artifacts has issues dealing with subdirectories Major ResolvedResolved
BAM-561 Configure dependencies in the opposite direction Major ResolvedResolved
BAM-493 Better handling of large number of unit tests Major ResolvedResolved
BAM-146 Build time graph should use minutes in scale Major ResolvedResolved
BAM-1173 Add an option to use a non Ajax diashboard "hideDashboard" Minor ResolvedResolved
BAM-1124 Crowd 1.0.6 + Bamboo 1.0.4 NoClassDefFoundError: com/atlassian/user/security/authentication/InvalidPasswordException Minor ResolvedResolved
BAM-792 Pass in bamboo parameters such as project and plan key to builders Minor ResolvedResolved
BAM-604 API access to the SCM repository's build identifier for a given build Minor ResolvedResolved
BAM-681 Checkboxes for build queues Trivial ResolvedResolved
BAM-680 Picker for e-mail notifications Trivial ResolvedResolved

If you want to check out a live Bamboo instance, take a look at our opensource instance.


Document generated by Confluence on May 08, 2007 23:47