I’m wondering what will happend if I set multiple releases (same project) to be deployed at the same time (using “When”)?
Will all be deployed or will the new scheduled" deployment cancel the prevoius so that only the latest release will be deployed?
The background to this question is that as a part of CI we want to deploy, at the moment, the latest release at 7.00,10.00,12.00 and 15.00 every day. I know that this is possible using Scheduled Tasks and octo.exe, but if it’s possible to use “When” to only deploy the latest I would prefered that solution.
(To minimize the impact on testing we don’t want to deploy immidiately)
Thanks for reaching out. Unfortunately recurring scheduled deployments are not something we support at the moment. We do have though a Uservoice suggestions that could us some of your votes if you’d like to see this implemented in the future.
At the moment your best shot is still scheduled task/build + Octo.exe
Hi, it’s not recurring deployment feature I’m thinking of. The question is: What’s going to happend if I set multiple deployments (different releases same project) to be deployed at the same time. Will all be deployed at the given time or just the last? If all are deployed, which one will be deployed last?
And there is no knowing which one will be deployed last? They will be deployed in the same order you scheduled them. If you need them to run in a specific order, I’ suggest you to schedule them with some minutes between them (seconds are not supported)
All is deployed to the same project and same environment. Which version would the UI show? The UI will always show the latest deployment that has been scheduled. See attached screenshot
