Problem / Gap
Currently, template authors don’t have a reliable way to define post-release actions that run automatically at the end of a release regardless of outcome (e.g., Completed, Aborted, Failed, Terminated). As a result, important housekeeping and operational tasks often require manual intervention and can be missed—especially when releases are aborted or force-terminated.
Request
Add the ability for a template author to define Post-Release Actions that will execute automatically whenever a release ends, independent of release status.
These actions should be configurable via:

Predefined actions / plugins (built-in options)
Custom scripts (e.g., Python or supported scripting mechanism)

Examples / Use Cases
Post-release actions could include:

Reporting / auditing (e.g., capture reason for manual abort / termination)
Cleanup tasks (e.g., revert temporary config, delete runtime artifacts, unlock resources)
Jira integration (e.g., update ticket status, add comment, transition workflow)
Notifications (e.g., notify a team channel/email on completion/abort with summary)
Metrics / dashboards (e.g., push final state + timestamps to reporting system)

Expected Behaviour

Post-release actions should run:

On successful completion
On abort / termination
On failure


Actions should support:

Ordering (multiple actions in sequence)
Conditional execution (optional: only on abort, only on failure, etc.)
Error handling (optional: continue on error vs stop; retry rules)


Execution should be traceable:

who configured it, what ran, when it ran, status/log output



Value
This feature improves reliability and operational hygiene by ensuring key closure activities are automated and consistently applied, reducing manual cleanup effort and preventing incomplete follow-up steps after aborted or failed releases.

by: YINFENG X. | 3 days ago | Templates & Releases