We plan to use the “manual intervention” step as a way to allow developers to mark a release as “ready for QA” by promoting it to QA with a manual intervention step so that when we actually want to deploy to QA, the proper people can just approve the intervention. However, since a developer may do this multiple times before the actual deployment (e.g. they mark a release as ready, add some more stuff, mark that release as ready, etc) and only the latest “deployment” will actually be approved, it seems like we would be left with a bunch of “deployments” hanging around that are waiting for approval. Is there a way to set it up so that when a developer “deploys” to an environment with a manual intervention step, all previous “deployments” that are waiting on a manual intervention are aborted?
Sorry for all the quotes, by the way; I used them to distinguish between an Octopus “deployment” and the actual deploying of components to a server (i.e. a completed deployment)