We're running Bamboo 5.9.10 using MySQL v5.5.41. We want to migrate to PostgreSQL 9.2 before upgrading Bamboo to v5.14.3. It's recommended to run an Export on Bamboo, start a new instance, and choose Postgres as the back end, and then run an import. We have 292G worth of Artifacts, so it would be unreasonable to have Bamboo include them as part of the export. We also have lots of logs.
My question is, if I don't include artifacts, nor build logs, nor results, but keep them in place on the filesystem. Will Bamboo be able to find them after starting a new instance and using importing the exported file? Will it try to overwrite them in the space that they are in?
So i did mostly that a few months ago...
Essentially, i did an export with everything BUT artifacts (our database is quite large already)
My steps included starting up brand new instance, going through the setup wizard to fresh empty bamboo instance (existing license).
After that, i imported my exported file (which took forever!!!, over 24 hours-36hours). once that was finished, i shutdown the instance..
here is where i copied the original artifacts directory from the old instance home, to the new instance home.. In fact i actually moved it, since it was about 1 terabyte..
When i brought the instance back up and navigated to the builds and corresponding artifacts, bamboo was able to find them no problem..
BTW. the reason i went through the setup wizard completely, and not used its import setup was that was told that the import from the Setup in some odd circumstances can be flaky.. It was recommended to me to run it after the blank instance was running fully..
Other tip.. start from a completely empty BAMBOO_HOME for the new instance, otherwise again you might run into odd issues..
It's good to know that the artifacts can be moved separately. The logs (and possibly build results?) are just text files as well, so I'd like to not needless copy and around large amounts of data.
Though this is making lean more towards trying a straight up database migration from MySQL -> PostgresSQL. Do you remember about how long your initial export took? It looks like the safest way to do that is to pause the Bamboo server, which would even further add to the downtime.
The export took about 3 or so hours, and i had the server in Pause mode, so people could get to things just not kick off new builds.
I researched doing a straight database -> database conversion, but all the tings i found seem iffy at best, and i lot of work to verify the mapping. We did all our products to PostgreSQL so i choose to do the vendor recommended route.. Bitbucket by far the easiest.. It has a conversion process builtin to go from one DB to another..
Hi all Lets make this Friday fun really fun and post one (or more) of your best jokes! The joke can be about an Atlassian product, or just a really fun joke you want to share! I’m not the best j...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot