Dashboard UI Implementation for Pipelines and Tasks

[kimholmes]

Expected Behavior

The portion of the Dashboard UI for Secrets should use design patterns and components for Carbon 10 and reflect the user experience created through collaboration between Development, Design and User Research

Actual Behavior

The actual behavior is found in the current implementation of the Dashboard UI

Design Specs for Pipelines:

At the following site, please find these three pages with specs for Pipelines:
https://kimholmes.github.io/Exported-Specs/PipelinesAndTasks/Pipelines/
Use the left nav to access the following pages:

Pipeline Main List View:

Pipeline Row Selected:

Pipeline Filtered List:
If the user clicks on a Pipeline in the above page, the result is a filtered list of PipelineRuns

Design Specs for Tasks:

At the following site, please find these three pages with specs for Tasks:
https://kimholmes.github.io/Exported-Specs/PipelinesAndTasks/Tasks/
Use the left nav to access the following pages:

Tasks Main List View:

Tasks Row Selected:

Tasks Filtered List:
If the user clicks on a Task in the above page, the result is a filtered list of TaskRuns

[AlanGreene]

For the PipelineRun and TaskRun status columns should we include the existing status text as a tooltip on the icon / in some other way (or leave it out entirely)?

Sample status text (these come from the environment):

• All Tasks have completed executing
• PipelineRun "output-pipeline-run-r-5mljg" was cancelled
• TaskRun demo-pipeline-run-6-build-skaffold-app-k4wxt has failed
• All Steps have completed executing
• "step-build-and-push" exited with code 1 (image: "docker-pullable://gcr.io/kaniko-project/executor@sha256:d9fe474f80b73808dc12b54f45f5fc90f7856d9fc699d4a5e79d968a1aef1a72"); for logs run: kubectl -n tekton-pipelines logs demo-pipeline-run-6-build-skaffold-web-m7kcm-pod-5c73f8 -c step-build-and-push

These would be the same values we currently display in the Status column

[kimholmes]

@AlanGreene That's a very good question and my first intuition was to put those in a tooltip. Especially since they can be as long as the one in that last bullet. It seems like they do often have useful information. Do you agree? I am worried about the toolitp being too long though. We might need to allow a certain amount of characters and then cut it off.

[AlanGreene]

I didn't actually notice the tooltip in the first PipelineRuns image yesterday, looks like you'd already thought of it 😆

Truncating the text in the tooltip is fine, the user should have enough info to know whether it's interesting or not and can still get more information by navigating to the page for the failed run.

I suspect that most of the time the status text will be relatively short and fit a reasonable size limit. The longer ones probably aren't best read in a tooltip anyway so just including enough to indicate whether the failure is "interesting" should be fine.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[AlanGreene]

/remove-lifecycle rotten
/reopen

[tekton-robot]

@AlanGreene: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[AlanGreene]

This issue is still valid. We're introducing batch delete for PipelineRuns and TaskRuns, and should have the same for both Pipeline and Tasks for consistency.

Items specific to TaskRuns are tracked in #776

[AlanGreene]

/kind design