BAM-5006, a customer request, resulted in ${bamboo.custom.svn.revision.number} no longer meaning the latest revision in the repository, but the latest change revision. While I can see the use case that make the latter interesting, this breaks our configuration, as we have multiple bamboo builds that are fed into a central one.

For example, we have a module A build (FOO-A) and a module B bamboo build (FOO-B). FOO-B is a dependent of FOO-A. Each has a separate location of a shared svn repository.

If the repository is at revision 5, we build the works:

• FOO-A = svn r5
• FOO-B = svn r5

Now we update a file for FOO-A and rebuild. We get inconsistent results:

• FOO-A = svn r6
• FOO-B = svn r5

It looks like B hasn't consumed A's changes... but it has. It also makes FOO-B look like a duplicate build with no changes, when it isn't.

Consider restoring this behavior of ${bamboo.custom.svn.revision.number} and adding something like ${bamboo.custom.svn.lastchange.revision.number}