Tags: kobaji/dashboard
Tags
Update PipelineRun container logic to correctly select TaskRuns with … …conditions The `tekton.dev/pipelineTask` label is applied to both the condition check TaskRun and the owning TaskRun. The previous logic could in some cases incorrectly select the condition check for display in the UI. Update the logic to ensure a match for the `tekton.dev/pipelineTask` label is only counted when there is no accompanying `tekton.dev/conditionCheck` label. This will ensure the condition is only matched when the selected value appears in the conditionCheck label, regardless of the order TaskRuns are listed in the data.
Use pipelineTask name for PipelineRun URL addressability Instead of using the TaskRun uid + pod name in the URL to address a specific TaskRun retry, use the more user-friendly pipeline task name and a separate retry parameter. This produces a more user-friendly URL, is more easily constructed by pipeline authors, and doesn't rely as much on kubernetes-isms (i.e. pod name). This change is based on feedback from preview users.
Fix display of array params Rename `WithLineBreaks` component and expand its purpose to handle rendering of all param types, not just strings. The newly named `Param` component will output params as YAML, this ensure that strings (including multiline) and arrays are formatted and displayed in a user-friendly manner.
Sort steps by timestamps in a TaskRun Currently, all injected steps appear before the regularly defined steps in some views. Now they are sorted by the finishedAt timestamp in each step's status, with ties broken by the startedAt timestamp. The current order is not always correct, since some injected steps actually run after regular steps. This ordering also causes some steps to be incorrectly labelled as either skipped or failed. The new order should be better, but it will still depend on the precision of the timestamps: seconds might not be sufficient in all cases. There are plans in 'pipeline' to increase the precision. Fixes tektoncd#1367 Cherrypicked for tektoncd#1438
Sort steps by timestamps in a TaskRun Currently, all injected steps appear before the regularly defined steps in some views. Now they are sorted by the finishedAt timestamp in each step's status, with ties broken by the startedAt timestamp. The current order is not always correct, since some injected steps actually run after regular steps. This ordering also causes some steps to be incorrectly labelled as either skipped or failed. The new order should be better, but it will still depend on the precision of the timestamps: seconds might not be sufficient in all cases. There are plans in 'pipeline' to increase the precision. Fixes tektoncd#1367 Cherrypicked for tektoncd#1438
PreviousNext