Bitbucket Upgrade Path

[Joshua Dowsett]

Hi,

I’m an Atlassian consultant working with a very large international customer (cannot disclose further) on an upgrade and AWS migration from their existing on premises instance.

They currently utilise Bitbucket 6.2.0, and plan to upgrade to the latest LTS release, 8.19.
Your app is currently on version 2020.09.05, and we are targeting an update to 2023.12.27.

Are you able to provide information on if we could encounter any potential issues when performing this upgrade? If there any conditions or additional steps we need to take in order to ensure the app is updated correctly and functions as intended.

Kind regards,

Josh Dowsett

‌

[Joshua Dowsett]

Additionally, the client makes use of Control Freak. This is on version 2020.09.22 and version 2024.04.01 is targeted. Is there any consideration here also?

[Joshua Dowsett]

And lastly sorry. The client also uses Commit Graph. This is on version 2022.02.07 and we will be upgrading to 2024.03.31. Are there any concerns here?

[Julius Davies [bit-booster.com]]

Hi @Joshua Dowsett - thank you for your questions! Sorry for the slow response (we’re at the Atlassian Team 24 conference right now).

‌

Regarding “Commit Graph”: all upgrades from all previous versions should be fine and uneventful.

Regarding “Control Freak”: all upgrades from all previous versions should be fine and uneventful.

Regarding “PR-Booster”: for most customers the upgrade was seamless. But 2 customers (out of hundreds) did need to clear bit-booster clones directory. You can clear this ahead of time using the older PR-Booster’s admin screen and clicking on the “Delete Temporary Clones” button (from the global admin page for PR-Booster). Alternatively, if after the upgrade the “bbClones” directory (under $BITBUCKET_HOME/caches) is still present, we recommend that it be deleted manually (e.g., “rm -rf”). Please be very careful to only delete the “bbClones” directory since everything else under $BITBUCKET_HOME is critically important!

The good news: PR-Booster uses dramatically less disk space now!

Finally, please invite your client to try out our “Git Graph for Jira” plugin !!! It’s free, and it’s a great addition to “Commit Graph” in our humble opinion. Here’s a link to it: https://marketplace.atlassian.com/apps/1215835/bit-booster-git-graph-for-jira?tab=overview&hosting=datacenter

[Joshua Dowsett]

Hi Julius,

‌

Apologies for opening this ticket back up. I was hoping to receive some clarity regarding your suggestion:

“Regarding “PR-Booster”: for most customers the upgrade was seamless. But 2 customers (out of hundreds) did need to clear bit-booster clones directory. You can clear this ahead of time using the older PR-Booster’s admin screen and clicking on the “Delete Temporary Clones” button (from the global admin page for PR-Booster). Alternatively, if after the upgrade the “bbClones” directory (under $BITBUCKET_HOME/caches) is still present, we recommend that it be deleted manually (e.g., “rm -rf”). Please be very careful to only delete the “bbClones” directory since everything else under $BITBUCKET_HOME is critically important!“

‌

Could explain the exact this would have? I’m trying to understand whether this is a breaking change that could affect our users after the upgrade.

‌

Thanks!

[Joshua Dowsett]

Any update on this?