Allow Scheduled Deployment Triggers to not re-deploy if targets are up to date
Currently, the Scheduled Triggers option allows setting a time to deploy, and even includes examples in the documentation for "nightly deployments." The downside currently is that it will re-deploy every single night, even if the environment was already successfully deployed to.
It would be nice to add an option to only deploy if the environment / targets need it done. This would allow for a real nightly promotion without excess deployments and logs.
9
votes
Chris Camburn
shared this idea
-
Matt Douston
commented
Implementing this would save so much time and networking resources for organizations that auto deploy dozens of modules to a test environment several times a day!