In digital.ai Release could we have a failure handler on the release (i.e.: when a release fails, execute some tasks, to ensure clean up and close related items). This would be similar to the failure handler on the task.
by: Garry D. | over a year ago | Templates & Releases
Comments
Thank you for the request, Garry.
We will look for a broader set of users voting and providing their feedback.
To better understand the need, could you explain the usage scenario:
- What action or series of actions would you execute after the release fails?
- Who would you expect to set up those actions? Release admins globally for all releases or each release owner individually?
Responding to this as another interested customer:
- What action or series of actions would you execute after the release fails?
-- I can actually think of quite a few:
* Define additional action, as for the task failure handler (basically jython code)
* Abort release
* Skip to phase/task
* Restart from phase/task with Original/Latest version
* Trigger another release from template
* Any other scenarios the product team can think of as well, as I think this feature has a lot of potential to tackle a lot of use cases and scenarios for customers
- Who would you expect to set up those actions? Release admins globally for all releases or each release owner individually?
-- I would say release owner individually. If someone has the permission to Edit a template, that person should also have the permission to edit release failure handler. And this sentence made me realize that you mentioned Release admin, not Template admin, so, in my opinion, these actions should probably have the same permissions as Task Failure handler permissions and the design idea should be that customers will set this up in the template, not in a running release.
Thank you!
Adding more additional feedback from our team: A Release Abort Handler would also be useful. Maybe it can be used to run python code or trigger another release from another template for cleanup operations for example.