You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Our current production Bamboo server is version 6.0 running as AWS EC2 instance (with 2 volumes) integrated with Postgresql RDS DB and JIRA user management.
I'm working on Bamboo upgrade to 6.6 and my challenge is that there is no any testing environment where I can test the upgrade first. so I'm looking for the best approach for backup of current server so in the case something goes wrong I can roll back fast to minimize server downtime.
Is creating AWS snapshots for Bamboo server's volumes a good enough path to follow to make sure the upgrade is easy revertible? I did read the documentation here: https://confluence.atlassian.com/bamboo/cloning-a-bamboo-instance-289277407.html
and I'm obviously going to export data as advised, but I need to be on the safest side that I can also revert the change quickly.
I suggest the following steps:
The Bamboo upgrade path has been relatively smooth and reliable in our environment so hoping you won't have any issues! And according to https://confluence.atlassian.com/bamboo/bamboo-upgrade-guide-720411366.html#Bambooupgradeguide-upgrade_pathDetermineyourupgradepath 6.0 > 6.6 looks like it should be a single upgrade - no need for an intermediary step.