We are running the octopus deploy integration in vsts version 1.2.81. Last time we upgraded we had to manually go through and fix all our build steps it used as it cleared out values we had in certain fields. If we upgrade to the latest version 2.x.x are we going to have to do the same thing?
Sorry for the delay in replying, I was running a few tests.
I’ve added some documentation to explain the upgrades and compatibility.
There is a breaking change between version 1.2.x and 2.x because we’ve changed the way the extension connects to Octopus. So to use the new version, you will have to modify the steps. However, most of the fields should carry over when you upgrade, and assuming you’re running TFS 2017 Update 1, you can upgrade the extension and the builds will still use the old version (and the old fields) until you’re ready. You can choose whether to upgrade the steps in the build definition on a case-by-case basis.
I hope that helps!