Currently, aborting a release requires all in-progress tasks to be manually aborted first. If multiple tasks are running in parallel, each one must be individually stopped before the release itself can be aborted.

In our case, we have several long-running JIRA polling tasks that remain in progress until a target status is reached. These tasks also include failure handlers configured to automatically retry on failure (e.g., during JIRA downtime), which prevents them from entering a failed state. As a result, aborting these tasks involves additional steps—disabling the failure handler, aborting each task, and only then proceeding to abort the release.

This process is time-consuming and operationally cumbersome.

We propose adding a force abort capability (via both REST API and UI) to immediately terminate an active release along with all associated tasks. This would significantly simplify cleanup of unwanted or stuck releases.

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