Manually skipped steps should also be skipped during auto-deploy

[michaelnoonan]

Steps that are skipped as part of a manual deployment of a project should also be skipped when running an automatic deployment of the project.

At the moment we forget the steps that were skipped in the manual deployment, and attempt to run ALL steps during an automatic deployment. We think this would lead to unexpected results...

Auto-deployments are intended to "make a new machine just like the other machines" - like auto scaling a web farm. If certain steps were skipped to the existing machines during a manual deployment, we should also skip the same steps when automatically deploying to a new machine so it has the best possible chance of ending up just like its counterparts.

[octoreleasebot]

Release Note: Steps that were manually skipped during a deployment will also be skipped during subsequent automatic deployments

[JesseNaranjo]

Does this apply only within the same Release?

For example - I create Release 1.0.50 and skip step 5. Will creating Release 1.0.51 (whether manually or automatically) auto-skip step 5 too?

[matt-richardson]

Hi @JesseNaranjo

The base premise for the auto-deploy is to bring all machines into the same state, so in your example, it will only skip step 5 when auto-deploying 1.0.50.

If you create 1.0.51, and deploy it without skipping any steps, it will not auto-skip any steps.

There's some pretty comprehensive docs on automatic deployment triggers, so feel free to take a look for further info.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.