Applying following configuration of a Project

• Pooling on SVN Repository
• Build Goals : clean package deploy release:prepare --batch-mode release:perform

In SVN Repository :

• the build-number.txt is added in svnignore
• The current Project Version is set to 1.0-SNAPSHOT

At the first execution, the Build perform all goals correctly :

• clean and package provide a new SNAPSHOT binary
• deploy deploys the 1.0.0-SNAPSHOT on Maven Repository
• release:prepare --batch-mode defines the release informations in release.properties on build Dir.
• release:perform releases the project by :
  • Updating version from 1.0.0-SNAPSHOT to 1.0.0
  • Releasing the 1.0.0 to TagBase URL
  • Updating version from 1.0.0 t o*1.0.1-SNAPSHOT* in the trunk
  • Extract of release 1.0 in Build.Dir.\target\checkout
  • deploy and site-deploy execution, providing a new released binary

After execution, a new release is tagged on SVN and the SVN Trunk is ready for the next SNAPSHOT release.
The Maven repostory is updated with SNAPSHOT and RELEASE repository.

But sadely, in the next pooling phase, Bamboo reexecutes the Build, because, there are two new changes :

• [maven-release-plugin] prepare release maven-checkstyle-plugin-config-1.0.0
  • /sfri/trunk/maven-checkstyle-plugin-config/pom.xml (version 7661)
• [maven-release-plugin] prepare for next development iteration
  • /sfri/trunk/maven-checkstyle-plugin-config/pom.xml (version 7663)

Then, each Build make some changes, then after each SVN pool, the Build is restarted.

What is the best way to manage release from Bamboo whitout having more than one plan per SVN URLs ?

The only short term solution, should be to launch a scm:update goal after the release.

• Build Goals Tested : clean package deploy release:prepare --batch-mode release:perform scm:update
• Build Goals not yet tested : clean package deploy release:prepare --batch-mode scm:update release:perform

What may be the best practice ?

Rgds