RELEASED: Public: March 5, 2025
Resolved issues
- The
triggerRemoteJobPipeline step now tracks build numbers of in-progress downstream builds in certain 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 record build numbers in metadata. -
confirmStartedrecords build numbers in metadata once the downstream build starts, as long as the job starts within the configuredtimeouttime span for the step. -
awaitResultonly records build numbers in metadata once the downstream build finishes.