We are currently live with Bamboo 2.7.3 and everything is running fine. We have a custom command line tool for Windows that preps our code before the release, pulling in the right version of various mercurial repositories
I am currently checking that everything works as expected in Bamboo 3.2 before we upgrade. It all looks good apart from one case where the command line tool takes takes a parameter that has spaces. In Bamboo 2.7.3 we just wrapped this value with double-quotes as you would on the command-line and everything worked fine.
In Bamboo 3.2 the double quotes seem to be being removed, thus breaking the call to the command line tool. There are a couple of other issues on the forums here where people seem to have had issues where double quotes have been in arguments defined in Bamboo. Has the way of defining this sort of thing changed?
An example of the arguments that I am trying to pass to the command line tool is
/r:"Build Phase 3" /b:default /w:c:\build\debug\Build3\x86\continuous\default /c:Debug /bv:${bamboo.buildNumber}
The first value seems to have its double quotes removed before reaching the command line, causing the tool to see a repo of "Build", invalid paramaters of "Phase" and "3" rather than a repo of "Build Phase 3" (without quotes)
