You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(taskspec): ensure TaskRun.Status.Steps ordering matches pod execution order
The TaskRun.Status.Steps list was not guaranteed to reflect the true
execution order when StepActions were involved, causing confusing behavior
in dashboards like Tekton Dashboard where steps would appear to "pop" into
view and reshuffle.
This change addresses three related issues:
1. Steps populated from StepAction resolution appeared first in Status.Steps,
while inline steps were only added later during pod-based status
reconciliation, creating a mismatch with actual execution order.
2. When TaskRuns used StepActions, inline steps were missing from
Status.Steps during the resolution phase, contributing to the ordering
confusion.
3. The final Status.Steps ordering didn't match the pod container sequence,
making it difficult for dashboards to display accurate step progression.
The fix ensures that:
- Status.Steps are populated for both StepAction-backed and inline steps
during resolution, even when there is no StepActions involved
- The final Status.Steps ordering is aligned with the pod step container
sequence by creating a temporary slice and replacing trs.Steps in one shot
- Existing Provenance information is preserved for matching steps by name
0 commit comments