Bamboo 4.4 : Bamboo 2.2 Release Notes
This page last changed on May 06, 2012 by pwatson.
9 March 2009
The Atlassian Bamboo team is proud to release
Bamboo 2.2.
Bamboo 2.2 introduces a range of exciting new features and improvements. Harness the flexible online processing potential of the Amazon Elastic Compute Cloud (EC2) to power your builds with the new Elastic Bamboo feature. This provides you with the power to reduce your build times as well as the flexibility in capacity to minimise costs.
Bamboo emails have been redesigned in this release. HTML templates are now supported and can be easily customised to your liking. We have also added new notification events in Bamboo, to allow you to collaborate more easily via build comments or detect when your builds hang.
Finally, we've implemented a few refinements to Bamboo builds. These include improving the performance of artifact transfer from remote agents and adding the ability to use the same repository snapshot revision for dependent builds.
Please note, this release contains a number of important security fixes. Please see Bamboo Security Advisory 2009-03-09 for further details.
Upgrading to Bamboo 2.2 is free for all customers with active Bamboo software maintenance.
Highlights of this release: | Thank you for your feedback:
over 68 new features and improvements implemented over 170 votes fulfilled
Your votes and issues help us keep improving our products, and are much appreciated.  Please keep logging your votes and issues. They help us decide what needs doing! |
Highlights of Bamboo 2.2

| Elastic BambooCloud computing comes to Bamboo with the introduction of the Elastic Bamboo feature. You can now configure your Bamboo application to create remote agents in the Amazon Elastic Compute Cloud (EC2). We've also incorporated a number of useful tools with this feature, that allow you to start up your builds more quickly via build snapshots, run Elastic Bamboo builds from behind a firewall and control Elastic Bamboo via the Bamboo REST API. 
|

| Customisable Email TemplatesBamboo emails have been given a facelift in this release. Multi-part (MIME) format is now supported allowing you to use HTML in your email templates (e.g. for Bamboo notifications). We've set up Freemarker templates in Bamboo as well, making it easy for you to customise the look and feel of your emails. 
|

| The new build comment notification event makes it even easier to collaborate in Bamboo. You can set up Bamboo to notify selected users and groups when a comment is posted against a build. Users can be notified by email, instant message or even RSS feed, depending on their preference. 
|

| Hanging Build Detection EventWe have also added a notification event for hung builds. Ensure that the right people are informed when a build hangs, by setting up notifications using this event. Users can be notified by email, instant message or even RSS feed, depending on their preference. 
|

| Faster Artifact TransferWe have dramatically improved the speed of artifact transfer from remote agents in this release. Remote builds with large artifacts will complete much more quickly, particularly over high-latency network links. |

| Dependent BuildsBuilds are now more consistent when triggering a build after another build finishes. If a child build uses the same source as the parent build, the child build will now be forced to check out the same revision of source code as the parent build. |

| Agent ImprovementsWe have introduced a remote agent supervisor in this release to monitor and automatically restart your remote agents, if necessary. You should notice an improvement in the uptime of your remote agents with this change. |

| Plus over 80 fixes and improvements
JIRA Issues (115 issues) |
Key |
Summary |
Priority |
Status |
BAM-3607
|
Builds should be able to have a configurable timeout threshold
|
|
Resolved
|
BAM-3605
|
CLONE -The LATEST URL redirect(s) only apply to top level artifacts.
|
|
Resolved
|
BAM-3591
|
Initial logging level of Remote Agent is DEBUG
|
|
Resolved
|
BAM-3561
|
Bamboo uses db column name "resource", this is reserved in Oracle
|
|
Resolved
|
BAM-3554
|
inconsistent slashing on View Instance page
|
|
Resolved
|
BAM-3553
|
Elastic Bamboo Configuration administration tab should be always visible
|
|
Resolved
|
BAM-3521
|
Agent Martrix should limited to active plans & agents
|
|
Resolved
|
BAM-3509
|
Restarting Remote Agent in wrapper causes license issues with 1 Remote Agent licenses
|
|
Resolved
|
BAM-3508
|
"Can't open file" error causes build to not be run
|
|
Resolved
|
BAM-3504
|
Plan Requirements Configuration page showing incorrect coloration and heading for images
|
|
Resolved
|
BAM-3480
|
Remote Agent creates spurious directory tree under the default bamboo home bin/ directory
|
|
Resolved
|
BAM-3479
|
Refactor VariableSubstitutionBean's so that their internal bamboo variables can be accessed by other components
|
|
Resolved
|
BAM-3462
|
Edit shared capabilities broken
|
|
Resolved
|
BAM-3458
|
Artifact copier fails to copy any artifacts if a target directory is missing
|
|
Resolved
|
BAM-3457
|
Make instance type of EC2instance available.
|
|
Resolved
|
BAM-3445
|
SVN UpdateEventHandler throws NPE
|
|
Resolved
|
BAM-3432
|
Shutdown all elastic agent fails
|
|
Resolved
|
BAM-3412
|
Change to SVN URL through global variables not detected
|
|
Resolved
|
BAM-3408
|
Evaluation Expiry message for all products
|
|
Resolved
|
BAM-3386
|
Cannot test IM notifications in Edit mode for non @talk.google.com accounts
|
|
Resolved
|
BAM-3341
|
All capability sets are imported as LocalCapablitySets regardless if they are remote or local
|
|
Resolved
|
BAM-3339
|
Elastic Bamboo implementation, M4
|
|
Resolved
|
BAM-3335
|
Elastic Bamboo implementation M3
|
|
Resolved
|
BAM-3329
|
Bamboo ships with out-of-date version of ehcache settings
|
|
Resolved
|
BAM-3292
|
Global Variables list in Administration panel is sorted randomly
|
|
Resolved
|
BAM-3281
|
Previous button on page '5. Artifacts' goes to '6. Notifications' instead of '4. Requirements'
|
|
Resolved
|
BAM-3280
|
Allow users to use the bootstrap jar directly
|
|
Resolved
|
BAM-3250
|
API for retrieving build artifacts
|
|
Resolved
|
BAM-3246
|
Remote build logging can slow down a build
|
|
Resolved
|
BAM-3243
|
Export fails with "Adding text to an XML document must not be null"
|
|
Resolved
|
BAM-3240
|
Local cvs repositories are not supported
|
|
Resolved
|
BAM-3220
|
Can not test IM client while in edit mode
|
|
Resolved
|
BAM-3194
|
Build Hang Prediction shows no logs for '299' minutes, even when messages are coming through.
|
|
Resolved
|
BAM-3189
|
Tests summary screen always shows last 25 builds
|
|
Resolved
|
BAM-3183
|
Test results directory can't be updated
|
|
Resolved
|
BAM-3179
|
Ability to delete comments
|
|
Resolved
|
BAM-3177
|
Artifact editing/viewing screens are inconsistent in the order of the columns
|
|
Resolved
|
BAM-3176
|
Latest status of a build may clear comment form
|
|
Resolved
|
BAM-3172
|
Allow underscore '_' character in Global Variable name
|
|
Resolved
|
BAM-3168
|
Ability to Abandon a build
|
|
Resolved
|
BAM-3166
|
Maven download logs should be filtered
|
|
Resolved
|
BAM-3155
|
Build Configuration | Builder | Test Result Directory not persisted for Bash (Command type)
|
|
Resolved
|
BAM-3141
|
Typo in LocalBuildResultProcessor 'Ignoriing'
|
|
Resolved
|
BAM-3138
|
Scheduled builds and builds running on remote agents don't seem to switch to a new source root in the build directory
|
|
Resolved
|
BAM-3125
|
Allow 'wget' unix utility to access plan's artifacts by providing username and password
|
|
Resolved
|
BAM-3122
|
Export of cusom data is not null safe
|
|
Resolved
|
BAM-3120
|
Ability to download artifact via the REST API
|
|
Resolved
|
BAM-3108
|
User Picker for build permissions lets you 2 when you can only add 1
|
|
Resolved
|
BAM-3105
|
Include failure details into Bamboo mail notification
|
|
Resolved
|
BAM-3104
|
Send Bamboo messages as HTML formatted mails
|
|
Resolved
|
BAM-3091
|
Incorrect error for editProfile when not logged in
|
|
Resolved
|
BAM-3090
|
Access artifacts from the standard "pretty" URL
|
|
Resolved
|
BAM-3089
|
Build results summary page relies on specific punctation in trigger reason.
|
|
Resolved
|
BAM-3083
|
Bamboo email notifications should include the unit tests that failed
|
|
Resolved
|
BAM-3043
|
Change logging level of AccessLogFilter from INFO to DEBUG
|
|
Resolved
|
BAM-2994
|
The LATEST URL redirect(s) only apply to top level artifacts.
|
|
Resolved
|
BAM-2991
|
SVN URL change is not picked up by all the agent.
|
|
Resolved
|
BAM-2989
|
Artifact collections with large numbers of small files take forever to copy
|
|
Resolved
|
BAM-2983
|
The remote agent dies if a (remote) build is stopped while artifacts are being transferred.
|
|
Resolved
|
BAM-2951
|
Add plugin point so that Agent/Build matching can be customised
|
|
Resolved
|
BAM-2946
|
Bamboo should display source repository revision used for particular build.
|
|
Resolved
|
BAM-2933
|
Ability to substitute to existing system variables for the System Environment field
|
|
Resolved
|
BAM-2852
|
Improve log transfer between Bamboo agent and build server
|
|
Resolved
|
BAM-2835
|
Bamboo should look for the BUILD FAILED message along with the BUILD SUCCESSFUL message to determine build out come.
|
|
Resolved
|
BAM-2803
|
Reduced log spam from remote agents
|
|
Resolved
|
BAM-2721
|
Artifacts should not be copied if builds fail.
|
|
Resolved
|
BAM-2713
|
Remove Errors From Dashboard
|
|
Resolved
|
BAM-2664
|
Tranfering artifacts of large size require too much CPU resources
|
|
Resolved
|
BAM-2612
|
Make latest artifact link an HTTP redirect instead of a meta-refresh browser redirect
|
|
Resolved
|
BAM-2606
|
Global Variables should be available in the Custom Data Map for a build
|
|
Resolved
|
BAM-2605
|
Bamboo doesn't trim spaces, when entering email addresses in the build notifications screen
|
|
Resolved
|
BAM-2560
|
Add links to order form on pages that notify customers their maintenance has expired
|
|
Resolved
|
BAM-2541
|
"Comment Added" Notification Condition
|
|
Resolved
|
BAM-2530
|
Scheduled Builds With no changes say, "This is an initial or manual build"
|
|
Resolved
|
BAM-2494
|
Bamboo home is logged as blank in the logs during start-up
|
|
Resolved
|
BAM-2479
|
Build Action status on "Currently Building ..." Screen doesn't update
|
|
Resolved
|
BAM-2475
|
Bamboo re-index code, doesn't handle cases where the buildresults XML file is null
|
|
Resolved
|
BAM-2466
|
Swap order of source directory and pattern columns in artifacts admin UI
|
|
Resolved
|
BAM-2450
|
Email Bamboo admins when builds start failing due to issues with the repository.
|
|
Resolved
|
BAM-2402
|
Reimplement "latest" artifact URLs as 302 redirects, rather than client-side refreshes
|
|
Resolved
|
BAM-2399
|
Document the ability to link to the latest version of an artifact
|
|
Resolved
|
BAM-2298
|
Allow for global variable substitution in the private key field, of the source repository page.
|
|
Resolved
|
BAM-2227
|
Dependencies should pass down meta data about the dependency chain
|
|
Resolved
|
BAM-2209
|
Only "stop build" is available from the Build Actions drop down menu even when the build has completed
|
|
Resolved
|
BAM-2198
|
The URL filter fails if there are special characters in the testcase name
|
|
Resolved
|
BAM-2168
|
Make Global System Variables accessible on the post actions page.
|
|
Resolved
|
BAM-2080
|
Elastic Bamboo implementation, M2
|
|
Resolved
|
BAM-2059
|
Directory clean on repository change may fail in distributed agent environment
|
|
Resolved
|
BAM-2047
|
trivial typo on plan Notifications screen: 'commited' should have a double 't'
|
|
Resolved
|
BAM-2018
|
Emails sent based on Build Notification
|
|
Resolved
|
BAM-1999
|
Add artifacts section to build notification emails.
|
|
Resolved
|
BAM-1991
|
"BUILD SUCCESSFUL" appearing shortly before a final "BUILD FAILED" message is misinterpreted as a successful build
|
|
Resolved
|
BAM-1839
|
Agent bootstrapper restart if server goes down / communication error occurs
|
|
Resolved
|
BAM-1831
|
HTML Emails
|
|
Resolved
|
BAM-1736
|
Incorrect message in error page when configuring notification for invalid groups/users
|
|
Resolved
|
BAM-1706
|
Ability to specify SMTP port in order to connect to SMTP server.
|
|
Resolved
|
BAM-1592
|
Ability to disable/delete IM Server
|
|
Resolved
|
BAM-1497
|
Next build arrow image has stray pixels
|
|
Resolved
|
BAM-1413
|
Support for MSBuild
|
|
Resolved
|
BAM-1403
|
Add more detail to the broken build e-mail - compiler error or broken test
|
|
Resolved
|
BAM-1396
|
Have a time limit on builds
|
|
Resolved
|
BAM-1394
|
Add "Build Actions" menu to Build Results page
|
|
Resolved
|
BAM-1375
|
Labeller plugin assumes that build log contains instances of SimpleLogEntry rather than LogEntry
|
|
Resolved
|
BAM-1360
|
Bamboo should explicitly build projects when user triggers a build ON manual build stratergy
|
|
Resolved
|
BAM-1355
|
Ability to remove Mail Server of IM Server Configuration
|
|
Resolved
|
BAM-1299
|
Improve the Notification Framework in Bamboo, to register listeners
|
|
Resolved
|
BAM-1177
|
Run builders on Amazon cloud
|
|
Resolved
|
BAM-1107
|
Broadcast IM comments
|
|
Resolved
|
BAM-947
|
Dependant builds of the same source tree should build the same source as the parent
|
|
Resolved
|
BAM-849
|
Ajaxy panels don't behave properly when a full page is returned from bamboo.
|
|
Resolved
|
BAM-846
|
Customisable emails.
|
|
Resolved
|
BAM-810
|
UI is left in a confused state on build failure
|
|
Resolved
|
BAM-695
|
Build email doesn't contain enough information in the case of build failure
|
|
Resolved
|
BAM-614
|
When a build fails I only want 1 error for artifacts
|
|
Resolved
|
BAM-509
|
Timeout builds when they take too long
|
|
Resolved
|
|