The question about automatically rolling back on failure keeps coming up, so I wrote a template that will re-deploy either the immediately previous release (if it was successful) or the specified version. It also allows for the input of prompted variables or use the values that were used in the last deployment.
Results
Adding this with an on error condition will re-deploy the version.
Before
It didn't exist before. That being said, scrutiny would be appreciated, poke holes in this if it's a bad idea.
After
It will give users an avenue to implement automatic rollbacks in the form of re-deploying a previous release.
Pre-requisites
[X] Id should be a GUID that is not 00000000-0000-0000-0000-000000000000
NOTE If you are modifying an existing step template, please make sure that you do not modify the Id property (updating the Id will break the Library sync functionality in Octopus).
[X] Version should be incremented, otherwise the integration with Octopus won't update the step template correctly
[X] Parameter names should not start with $
[X] Step template parameter names (the ones declared in the JSON, not the script body) should be prefixed with a namespace so that they are less likely to clash with other user-defined variables in Octopus (see this issue). For example, use an abbreviated name of the step template or the category of the step template).
[X] LastModifiedBy field must be present, and (optionally) updated with the correct author
[X] The best practices documented here have been applied
[ ] If a new Category has been created:
[ ] An image with the name {categoryname}.png must be present under the step-templates/logos folder
[ ] The switch in the humanize function in gulpfile.babel.js must have a case statement corresponding to it
Background
The question about automatically rolling back on failure keeps coming up, so I wrote a template that will re-deploy either the immediately previous release (if it was successful) or the specified version. It also allows for the input of prompted variables or use the values that were used in the last deployment.
Results
Adding this with an on error condition will re-deploy the version.
Before
It didn't exist before. That being said, scrutiny would be appreciated, poke holes in this if it's a bad idea.
After
It will give users an avenue to implement automatic rollbacks in the form of re-deploying a previous release.
Pre-requisites
Idshould be a GUID that is not00000000-0000-0000-0000-000000000000Idproperty (updating theIdwill break the Library sync functionality in Octopus).Versionshould be incremented, otherwise the integration with Octopus won't update the step template correctly$LastModifiedByfield must be present, and (optionally) updated with the correct authorCategoryhas been created:{categoryname}.pngmust be present under thestep-templates/logosfolderswitchin thehumanizefunction ingulpfile.babel.jsmust have acasestatement corresponding to it