RELEASED: Public: October 30, 2024
Resolved issues
- Excessive work when propagating item deletion in a High Availability (HA) controller (BEE-52251)
-
If an item (a job, folder, and so on) is deleted in a High Availability (HA) controller, or moved out of a folder, other replicas mirror the change. However these replicas duplicated some of the processing and events applied by the replica that performed the deletion, possibly leading to unwanted side effects. Now, the other replicas note it as missing from its containing folder or Jenkins root without further actions.
- Improperly cancelled build adoption in a High Availability (HA) controller (BEE-52252)
-
Under certain timing conditions, a build offered for adoption by an exiting replica in a High Availability (HA) controller can be assigned to another replica that itself is about to exit, leading to the build becoming temporarily orphaned. Now, the adoption processing logic handles this case more robustly, continuing to search for a new owner.