This weekend, I finally upgraded our Production instance of Atlassian JIRA to the latest release 5.2.11. It has been a long time coming really. I mean, we were still running 4.2 which I installed back in November 2010. I had been planning to upgrade JIRA at the end of 2011, but because of the complexity of doing a Manual Upgrade along with not having enough time to dedicate to the entire process, it kept getting delayed. Over the last month and a bit I had managed to do a test upgrade and migration to a new Windows Server 2012 server. It went smoothly and so I scheduled the upgrade of the Production environment.
The upgrade went mostly smoothly. I did get an error after the data import which was a bit daunting, but after restarting the JIRA service and reading through the logs it looked like it completed successfully and clicking around there didn’t seem to be anything wrong or missing. To make the migration even more challenging, I introduced proxying the JIRA instance through IIS using Application Request Routing. This is something I hadn’t used yet, but will probably play with some more. I also added changing the URL from http://server/jira to http://jira.domain.name, so there was redirect rules required. To top it all off, I also decided to migrate our existing Confluence across to the same new server as JIRA along with using the IIS proxying with ARR and make the same URL changes as JIRA.
The next step… start planning to upgrade our production Confluence instance to the latest release… have to upgrade to Version 4 first and then up to 5. Fun times ahead 🙂
Until next time!