Upgrading to v2019.3.1 - Breaking Change

Hi Support,

We plan to upgrade to v2019.3.1, but we have a few concerns.

Part of v2019.3.1upgrade:
In order to make use of the new Spaces feature, Tentacles should be updated to version 4.0.0, Octopus.Client dependencies should be updated to 5.0.0 and any other integrations should be updated to their latest version.

Our versions use the 3.0 Major Tentacle versions. Does version 4.0.0 of the tentacles cause any breaking changes? Since setting up tentacles on the new upgraded Octopus would automatically upgrade our current tentacles, we want to make sure nothing irreversible occurs.

  • We would first upgrade from our Octopus TEST server (which is v2018.12.1) to v2019.3.1.
  • Then we would upgrade from our Octopus PROD server (which is v2018.4.7) to v2019.3.1.

Have there been any other breaking changes other devs have made you aware of?

Thanks,
Alex

Hi Alex, thanks for getting in touch

The breaking change introduced by the Spaces feature applies only to Tentacle registration - if you want to register a tentacle to a Space other than the Default Space, then you need the 4.0.0 Tentacle. Earlier Tentacle versions can only be registered in the Default Space.

This means when you upgrade, all existing 3.x tentacles will continue to work as normal in the Default Space. Backwards-compatibility is something we paid a lot of attention to in this release

Hope this answers the question,

Thanks,

Jason

Thank you, Jason. I appreciate the response. We will move forward with the upgrade given this information.

Best,
Alex