RELEASED: Public: September 17, 2025
Resolved issues
- Aborting upstream jobs now correctly aborts all corresponding downstream jobs (BEE-60687)
-
Previously, in
triggerRemoteJob
awaitResult mode, aborting an older upstream job would fail to abort its corresponding downstream job if more than five newer upstream-to-downstream job pairs had started subsequently. The abort logic now ensures that the downstream job linked to any aborted upstream job is correctly terminated, regardless of its position in the build queue.