RELEASED: Public: March 5, 2025
Feature enhancements
- The
triggerRemoteJobPipeline step now tracks build numbers of in-progress downstream builds in some cases (BEE-55056) -
When using the
trackProgressAwaitResultmode of thetriggerRemoteJobPipeline step, the build number of the downstream job was not recorded in metadata used by build visualization tools, such as CloudBees Pipeline Explorer, until the downstream build completed. Now, the build number of the downstream job is available in metadata once the downstream job starts, as long as the job starts within the configuredstartedTimeouttime span for the step, which now defaults to one hour.
Note that other modes have different behavior. For example:
-
fireAndForgetandconfirmScheduleddo not track build numbers at all. -
confirmStartedtracks build numbers once the downstream build starts. -
awaitResultonly tracks build numbers once the downstream build finishes.
Resolved issues
- Improved CloudBees Pipeline Explorer robustness in case of corrupt build metadata (BEE-55458)
-
Previously, under specific conditions, JUnit-format test results in a Pipeline build running in an High Availability (HA) controller may be malformed. This caused CloudBees Pipeline Explorer to throw an error and block the display of the build results.
This issue has been mitigated; the malformed results are now logged, allowing the display to proceed.
Internal changes to streamline development. Not user visible. (BEE-54669)(BEE-54701)(BEE-55479)