As part of our release process, we update and tag a particular version of Confluence in CVS. Bamboo may or may not build this exact version, depending on what other commits occur around the same time. After tagging, we check out the tag locally and build and run the tests to make sure our tagged version is okay to release or deploy. As a build server, Bamboo should be able to do this.

To run a "release build" or "tagged build", the user would select a project, select a VCS branch and tag, and Bamboo would run the normal build process and capture artifacts, etc.

Bamboo should keep a list of "release builds" or "tagged builds" separate to the normal list of builds, since the normal list of builds has a useful chronological order which release builds would disrupt.

As a secondary enhancement, the release builds should be configurable separately to the normal builds. That is, they could configured to run different maven targets (including deployment, perhaps), and capture different artifacts (JAR and WAR files, for example).