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.- Unnecessary delays provisioning shared agents/clouds whose leases were recently returned (BEE-55432)
-
Previously, if a controller or a replica of an High Availability (HA) controller had leased all shared agents (or agents from a shared cloud) matching a given label, a different controller or replica of the same High Availability (HA) controller may be told by operations center that this label cannot be provisioned using the shared agent system.
This misleading information could be cached for up to five minutes even after some or all of the leases have been returned by the previous owner, blocking the new controller or replica from even asking operations center whether its outstanding queue items might now be satisfiable. The queue items would eventually be scheduled, but after an unnecessary delay during which the shared agents are idle, other controller or replica might unfairly lease them out of turn.
Now, the status of labels on the controller is tied only to the static configuration of the shared agents/clouds as defined on operations center. The current lease status is only considered when deciding whether to provide an agent.