-
Notifications
You must be signed in to change notification settings - Fork 268
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
Support pipeline matrix feature #2410
Comments
Thanks for the feature request @afrittoli and for adding the link in #2306. I think we'll have to tackle this one in at least 2 phases:
I'm hoping that 1 should be relatively straightforward to implement but will need to experiment with the feature to ensure we have all of the required information to reliably generate a stable UI + URL (e.g. there's a number appended to the pipelinetask name, need to ensure that this number or the expected display name is available in a label or other known field so we have a stable source for this info). For 2, this will require some more work and will be tracked as part of the larger redesign effort in #2306. We already have a similar issue with retries where each attempt is rendered in the UI as if it was an independent |
Some very rough testing for the first phase using the example at https://github.com/tektoncd/pipeline/blob/main/examples/v1beta1/pipelineruns/alpha/pipelinerun-with-matrix.yaml There are some issues rendering retries in the Dashboard with this update, and also possibly a bug in Pipelines where the PipelineRun is terminated without waiting for retries to complete (will be tracked separately). This POC also relies on some potentially brittle logic to get a unique display name for each TaskRun in the matrix, needs more testing, particularly with longer PipelineRun and pipelineTask names. Having the generated name We should also look at how the CLI is currently handling this and any planned changes / improvements there to ensure at least some sort of consistency: |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
This is something we still want to do, freezing so it doesn't get auto-closed. |
/area roadmap |
From user perspective, This is very critical issue to use matrix feature because there's no way to see failed logs in dashboard at all currently. +1 |
Hi @ileixe, thanks for your interest in this feature and apologies for the delay, I didn't see the notification for your message. I agree that it's important to have this functionality, and there is some work in progress to add matrix support. However, bear in mind that matrix is currently an alpha feature in Tekton Pipelines and subject to change. I have been doing some work on matrix support in the Dashboard this week. At this point I'm not sure which release it will be included in, either:
This plan is of course subject to change depending on changes in the functionality provided by Tekton Pipelines, results of testing, etc. Until matrix support is provided natively in the Dashboard you can view the logs by accessing the TaskRun details page for the relevant run(s). If you need to filter the TaskRuns list to find the relevant runs you can filter by PipelineRun name See for example on our dogfooding cluster, to get the TaskRuns for the 'unit-tests' tasks in the specified PipelineRun: |
Initial support for displaying matrix TaskRuns was released in Dashboard v0.39.0 Future releases will continue to improve on this. |
Some related proposals in Tekton Pipelines that will allow us to further improve the display of matrix TaskRuns in the Dashboard: |
Matrix display names are now supported in Dashboard v0.45.0, this feature requires Pipelines v0.58.0 or newer: https://github.com/tektoncd/dashboard/releases/tag/v0.45.0 |
Is your feature request related to a problem ?
This is related to a new pipeline feature - tekton matrix.
Matrix requires support for minimal status, which already implemented.
Dashboard today however only displays the first
TaskRun
in a matrix:While in fact there are many TaskRuns
Describe the solution you'd like
I think a basic feature would be to show all
TaskRun
in thePipelineRun
view.It would be nice to have the
TaskRun
that belong to a matrix visually grouped together somehow.Additionally it would be nice to highlight the parameters that are passed to the specific each
TaskRun
that come from the matrix.The text was updated successfully, but these errors were encountered: