-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve display of skipped tasks #3651
Conversation
Skipping CI for Draft Pull Request. |
a5cdeb6
to
f442079
Compare
f442079
to
3eac713
Compare
/test all |
3eac713
to
29ae602
Compare
/test all |
941d171
to
39fc8a3
Compare
39fc8a3
to
6b21f54
Compare
packages/components/src/components/DetailsHeader/DetailsHeader.jsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question but otherwise lgtm
When a task is skipped ensure this is communicated to the user instead of leaving it showing as 'pending'. In the case of when expressions, surface details of the when expression so the user can undertsand the reason for the task being skipped. Also remove elements that will never have content in this case such as the pod tab on the TaskRun details view, and replace the log container with a message indicating that the task was skipped and no logs will be available. Update the status icons and labels to differentiate between pending / not run and skipped. Apply similar changes for step-level when expressions which rely on the step actions feature being enabled.
6b21f54
to
02c864d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: briangleeson The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Changes
Note
This PR addresses a current gap in functionality, surfacing important information to the user to help understand the behaviour of a given pipeline / pipeline run.
It is a work in progress of one potential tactical change to improve the display of skipped tasks in the short term.
The design and/or approach may change drastically before it is merged.
However, a much larger and far-reaching redesign of the PipelineRun details page is still planned, see #2306 for details of some of the identified aspects. That change will likely involve updates to the navigation structure of the task list, the display of logs, and may also impact the way the 'skipped' status is surfaced.
Resolves #2293
Resolves #1445
When a task is skipped ensure this is communicated to the user instead of leaving it showing as 'pending'.
In the case of when expressions, surface details of the when expression so the user can undertsand the reason for the task being skipped. Also remove elements that will never have content in this case such as the pod tab on the TaskRun details view, and replace the log container with a message indicating that the task was skipped and no logs will be available.
Update the status icons and labels to differentiate between pending / not run and skipped.
Apply similar changes for step-level when expressions which rely on the step actions feature being enabled.
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes