Add support for display details of PipelineRun which uses Pipeline from Tekton Bundle

[mdreizin]

Describe the bug

Dashboard does not display any details of PipelineRun which uses Pipeline from Tekton Bundle:

---
apiVersion: tekton.dev/v1beta1
kind: PipelineRun
metadata:
  name: my-pipeline-1
spec:
  pipelineRef:
    name: my-pipeline
    bundle: grc.io/my-catalog/my-pipeline:0.1
  params: []

Expected behaviour

It would be nice to display details of such PipelineRun-s.

Steps to reproduce the bug

1. Publish Pipeline as Tekton Bundle
2. Create a simple PipelineRun which will use Pipeline from that bundle.

Environment details

• Kubernetes Platform: GCP

• Kubernetes or OpenShift version:

• Install mode (if on OpenShift): -

• Cloud-provider/provisioner: GKE

• Versions:
  • Tekton Dashboard: 0.17.0
  • Tekton Pipelines: 0.24.1
  • Tekton Triggers: 0.14.1
• Install namespaces:
  • Tekton Dashboard: tekton-pipelines
  • Tekton Pipelines: tekton-pipelines
  • Tekton Triggers: tekton-pipelines

Additional Info

A simple workaround is to publish a pipeline by kubectl to display missing details.

[AlanGreene]

Thanks for opening the issue @mdreizin. This is definitely something we want to add (surprised we didn't already have an issue tracking it…). @afrittoli I thought you had opened an issue on this but maybe I imagined it.

There are a few ways we could approach this, including using more information from the PipelineRun status instead of relying on the Pipeline and Task definitions in some cases.

Note: for anyone looking for more information on the bundles functionality, see https://tekton.dev/docs/pipelines/pipelines/#tekton-bundles

[mdreizin]

@AlanGreene Not at all! I am looking forward to arriving that feature.

[mdreizin]

Do you have any updates? :)

[AlanGreene]

No updates on this feature just yet. We're coming to the end of a major refactoring effort that touched almost every part of the application. Once that's complete we'll be reevaluating the open feature requests and this is one of the high priority items.

[mdreizin]

Thank you very much for sharing updates.

[mdreizin]

Also it would be nice to support Pipelines in Pipelines as well.

[AlanGreene]

@mdreizin I agree, we're tracking Custom Task support in #1970

[mdreizin]

@AlanGreene I will track that related issue 👀. Thank you for sharing!

[AlanGreene]

As discussed today, @briangleeson and Jerh will take a look at this over the next 2 weeks to determine the current state of Dashboard support for Tekton Bundles, and options for improving this based on information already available in the TaskRun/PipelineRun.

We need to test a number of scenarios where TaskRun / PipelineRun references bundles, including:

• no definitions applied on-cluster (i.e. all coming from bundles)
• definitions applied on-cluster match those from the bundles
• definitions applied on-cluster differ from those in referenced bundles

In all cases we should record what information is available in the TaskRun / PipelineRun that might allow us to reconstruct the required details, e.g. the taskSpec or pipelineSpec in the status field. Is this always available?

If there's not sufficient information available, what are the options to obtain it?

Once we have an accurate picture of the current state we can plan the required changes to add support.

[AlanGreene]

@mdreizin fyi, this is available in the latest nightly build and will be included in the upcoming Dashboard v0.22 release in the next week or so.

[mdreizin]

@AlanGreene Thank you for sharing great news! we will try to use it and I let you know.

[mdreizin]

@AlanGreene I am sorry for asking. Could you please share a link where I can find nightly builds?

[AlanGreene]

No bother at all. Latest nightly is at:

• default install https://storage.googleapis.com/tekton-releases-nightly/dashboard/latest/tekton-dashboard-release.yaml
• read-only install https://storage.googleapis.com/tekton-releases-nightly/dashboard/latest/tekton-dashboard-release-readonly.yaml

[mdreizin]

@AlanGreene We have just installed released version and it works well without any issues. Thank you very much for implementing it!

[AlanGreene]

Glad to hear it's working well for you