It would be very useful to have an option in the Create Release task to wait for the release it created to finish, something similar to the option of starting the release or not that is already present in the task. This would remove the need of adding the additional gate task to monitor the releases as all Create Release tasks could live in a Parallel Group task and all of them would finish and the release would move on only after all subreleases finished.
by: Andrei-Costin L. | about a year ago | Templates & Releases
Comments
When we were in the process of implementing the 'Create Release' task, we did explore this option. However, there were concerns about combining it and potentially resulting in a long-running task. In your scenario, does the 'Create Release' task exclusively generate subreleases at a single level, or could it potentially create additional releases beyond that level? The specific concern here is determining when to stop waiting for the original task to complete.
@DevOps Product team: I like Andrei's idea; we also often have a 'Create Release' task immediately followed by a gate.
I'd suggest that there should be a tick box in the 'Create Release' dialog labeled 'Wait for release completion'.
When checked, the Create Release task could have a shield icon next to the plus icon.
Thanks
We do sometimes go to multiple levels with subreleases (never more than 2-3 though). If potentially infinite running tasks are a concern (which I agree they are), I think a simple timeout config would address that. And it would be nice to have that customizable per task instance (as opposed to having it defined in deployit-defaults.properties), so for a template we can set it to 30 minutes and in another to 60, so that users can set the timeout depending on a maximum time they think it's appropriate for their process/subreleases to run for, allowing maximum flexibility and eliminating the risk of infinite waiting.
Linking duplicate idea: https://ideas.digital.ai/devops/Idea/Detail/4270
We could also use a wait for completion option.
In our use-case a main release creates sub-releases for individual deployments.
In most cases those deployments can run in parallel and it is ok that "Create Release Task" does not wait for completion.
But in some cases the deployments need to run sequential. In that case we currently have a sequential group that starts one sub-release then a "Wait for Delivery" task that waits for that sub-release to complete and after that start the next sub-release.
With the option to wait for the completion of a started sub-release the sequential deployment case could be greatly simplified.
@Christian K. you could use this potential new feature for parallel deployments with subreleases as well. You can put them in a parallel groups and the group will be done once all create release tasks that wait for the subrelease to be completed finish.