Upgrading Stash 2.3.1 to 2.7.latest - any pitfalls?

I am planning to upgrade our stash server from 2.3.1 to 2.7.2. Are there any in-between upgrades that I should do?

We are using the mysql database.

I have seen the notes about backing things up, after stopping the stash and mysql services.

Thank you.

2 answers

1 accepted

1 vote
Accepted answer

Hi John,

Our in-application upgrade should handle the relevant migration from any previous version of Stash.

However, there might be unforseen problems and we highly recommend backing up everything before performing any upgrade, just to be on the safe side. Posting this here just for completeness (and others).

https://confluence.atlassian.com/display/STASH/Stash+upgrade+guide

Just to double-check, did you see the warning at the bottom of that page about MySQL and binary logging?

Cheers,

Charles

Thank you Charles.

Yes I did. The notes for each release will warn you, when needed.

It turns out that we do not have binary logging turned on for MySQL, which I found out when I added the flag to /etc/my.cnf and MySQL would not start. Kudo's to the MySQL people for putting an error message in the log, that was understandable.

When I removed the binary logging setting to MIXED, it started up and no errors so far.

Regards,

John

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

212 views 3 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you