Do not install Bamboo 4.4.2 if you use Perforce

[Gail Stewart]

I have found much to like in Bamboo over the past two years, but this release is making me look at other CI servers. It's going to take me a week to recover from the upgrade. Going back would take a week too. There is a bug where it cleans the workspace because of the upgrade. For perforce users this is a disaster. I have to go though all 106 projects and force sync each of them.

I want a build server that does what I want it to do but knows that the the human is in charge not the software.

This release stinks.

[Nic Brough -Adaptavist- · Accepted solution]

Have you raised this with Atlassian Support?

Thanks for the warning of course, it could save some of us a lot of pain! Which version did you upgrade from though?

[Gail Stewart]

Yes - see BAM-12853. I upgraded from 4.2.1.

[Gail Stewart]

https://jira.atlassian.com/browse/BAM-12853 was report. It looks as though it will be released in version 4.4.4 and or 5. No indication when they will be shipped.

[Adam Myatt]

I believe Bamboo 4.4.4 was just released today that contains a fix for this issue.

[Edward Freedman]

I really wish I had seen this post before upgrading. I am not sure what to do at this point. There doesn't seem to be any reasonable way to downgrade the server (since all the agents have updated, as well as potentially the database schema). You would think someone would just release a tool which converts the repository xml files over to the new format out from under the agents, thus sidestepping the unwanted cleansing.

I am at a complete loss here.