Get product advice from experts

Ask a question →

Join a community group

Find a group →

Advance your career with learning paths

Take a free class →

Earn badges and rewards

Connect and share ideas at events

See the calendar →

Community
Products
Bamboo
Questions
Do not install Bamboo 4.4.2 if you use Perforce

Do not install Bamboo 4.4.2 if you use Perforce

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.

3 answers

1 accepted

2 votes

Answer accepted

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?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Reply

0 votes

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Reply

0 votes

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Reply

Suggest an answer

Log in or Sign up to answer

Was this helpful?

Thanks!

TAGS