Upgrading from 2.6 to 3.2 and the impact on Azure steps

In 3.0 you introduced a breaking change by removing Azure steps, but in 3.1 you re-introduced them. We’re about to upgrade from 2.6 to 3.2 using this guide: http://docs.octopusdeploy.com/pages/viewpage.action?pageId=3048133. Is there any special care we need to take to ensure our Azure steps will work correctly?

Hi Rob,

Thanks for reaching out. You are partially correct here: In 3.2 we re-introduced an Azure deployment method that’s very similar to the one in 2.6, but its not exactly the same. Unfortunately you’re gonna have to re-do the Azure steps using the new method when you migrate to 3.2.

Our recommendation is to do an Upgrade with a new 3.0 server instance, which will let you have both your Productive 2.6 server running, while you test the new 3.2 method on the other server. Once you know how the new azure steps work and you are ready to do the cutover, migrate your 2.6 data to your 3.2 server and re-do the Azure steps for your project.

Hope that helps,

Dalmiro

Thanks, Dalmiro. We are limited in the number of servers we have access to. Is installing Octopus 3.2 alongside the existing 2.6 version safe? We can put it on a different port to avoid clashes. Do you have any guidance on this?

Hi Rob,

You cannot install 2 different versions of Octopus on the same server. The 2nd one will leave the 1st one un-usable. You are gonna need another server for this.

Regards,

Dalmiro