RELEASED: Public: {2024-08-RELEASE-DATE}
Resolved issues
- Builds running in other replicas must be aborted before job deleted (BEE-31030)
-
When deleting a project (or a folder containing some projects, maybe in subfolders) Jenkins will first attempt to abort all running builds of the project(s) to avoid data corruption. This did not work in High Availability (HA) controllers when some builds were running on replicas other than the one with the sticky session, or otherwise processing the deletion event; for example, due to branch indexing. Now, builds on all replicas are aborted before the deletion is allowed to proceed.