Octopus Deploy uses a deployment snapshot until I create a new version

Question

I am trying to configure deployment in Octopus Deploy. Like many other developers, I do this through iterations: configure steps / scripts / packages → click “Deploy” → check the result → start over if we do not. In the case of Octopus Deploy, a snapshot of the deployment process is used if any steps / scripts have been changed since the last version. Basically, when it comes to deployment, I get this warning:

Warning. For consistency, this deployment will use a snapshot of variables and the deployment process that do not include the latest changes to the project. The changed process can be included only by creating a new version (if necessary, it can be renamed). Variables can be updated using the release page.

This means that I need to add a new version to check if the changes to the deployment script have entered or not. To add an issue, I need to update the version, etc.

My question is: how can I redo the same issue with all the changes to the steps made since the previous release? Is there a way to create a new release for this?

Answer 1

I asked this question to Pavel Stoval several months ago when I started working with Octopus. His answer was no.

I am afraid that there is no way to do this without creating a new version. When you create a release, Octopus deploy stores the object in an internal database, which is a snapshot in time that contains everything you need to deploy. It has no mechanism for updating these stored objects, so you need to create a new release every time.

Answer 2

Note that although a snapshot of the process is taking place, the variables can be updated if you redistribute the previous version. If you just change the values ​​of the variables, then yes, you can reuse the same release over and over again. If you change any process steps, then no - you need to create a new version.

If anything, the version number just helps keep the situation separate. The only time this becomes a problem is if you use NuGet for version control, but if you use standard version control of templates in Octopus deploy, this increases the number in the version number.

Answer 3

You can rename your failed version on the release page (in the section: Change this version). This way you can create a new release with the old version number and avoid unnecessary work.