I’d like to configure the deployment triggers so they deploy to the destination environment only if it has not been deployed to yet. I don’t want deploy triggers redeploying what’s already in a given environment in the most recent release.
I have a large number of projects with scheduled deployment triggers set to deploy from Development to QA at regular intervals. If the Development deploy has already been promoted to QA, I don’t want a subsequent scheduled trigger to redeploy to the QA environment if it’s already been deployed to. With how it is now dozens of deploys get queued up that are effectively redundant, wasting a lot of time in our task queue. My idea here is for the scheduled triggers to promote only new updates to QA, not redo things that have already been promoted from Dev to QA in the most recent release of a project.
Is this possible to configure in the UI? Does the Octopus REST api expose enough that I can create a script to do things this way? (For a project, get the default channel, check whether an environment has been deployed to or not, and if it hasn’t, trigger a deploy to it.)