Automatically retry steps if they are failed
Now when a step failed you have to set guided failure on in order to retry the step, it would be handy to have a setting where you say always retry failed steps.
For example if you are doing continues deployment where a build server triggers a deployment from a build, you have to:
- login into octopus
- select the correct project
- manually intervene and assign it to you
- retry it
It would be much better if the retry can be done automatically
Daan Le Duc
shared this idea
-
Lee Cherry
commented
This would also be useful in instances of locked files believe it or not. I have seen lots of instances whereby the deployment is waiting on a retry due to not being able to update a file, I don't do anything other than hit retry and it works. Suggests at that moment in time a file was locked.
Other instances where it would be useful is when multiple deployments are happening to the same machine, e.g. IIS websites, you may want to stop IIS for one for the sites to be deployed, and then start it again. If there were multiple different sites on the same box, it would be good to deploy all projects at once and let Octopus do the retry should IIS be stopped when it needs to be started
-
Domagoj
commented
I would need this if tentacle was offline, to do the deployment when it comes online.
In my place not every deployment targert in online all the time. -
Sujit Singh
commented
For Azure deployment steps I wonder if adding number of retry can be added in the step template as a parameter to achieve this.
-
Daniel
commented
We would also really appreciate a retry setting. Also having issues with failed azure resource group deployments that usually work on the first manual retry.
-
Glen Boonzaier
commented
We really need this for Azure deployments. I have to manually intervene about 6-10 times per deployment as steps often fail due to timeout or connectivity problems.
-
Corey
commented
This would be great, especially with the email step, sometimes the email step fails on connection to smtp and marks the whole deployment as failed even though that was the only portion that failed.