dashboard
dashboard copied to clipboard
tektoncd
Dashboard should show TaskRun sidecars + their logs
related issue for CLI: https://github.com/tektoncd/cli/issues/655
- https://github.com/tektoncd/pipeline/blob/master/docs/tasks.md#specifying-sidecars
- https://github.com/tektoncd/pipeline/blob/master/docs/taskruns.md#specifying-sidecars
- https://github.com/tektoncd/pipeline/blob/master/examples/v1beta1/taskruns/sidecar-interp.yaml
- https://github.com/tektoncd/pipeline/blob/master/examples/v1beta1/taskruns/dind-sidecar.yaml
- https://github.com/tektoncd/pipeline/blob/master/examples/v1beta1/taskruns/sidecar-ready.yaml
Yeah, this sounds like a great addition, asked @vdemeester for an example and https://github.com/tektoncd/pipeline/blob/master/examples/taskruns/dind-sidecar.yaml looks suitable for working with
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: 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: Reopened this issue.
In response to this:
/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.
I think it would be a good idea to consider this along with https://github.com/tektoncd/dashboard/issues/572 and https://github.com/tektoncd/dashboard/issues/1445 to ensure we provide a good experience and don't introduce too many different mechanisms for accessing errors / logs.
This might also benefit from some of the updates being made for https://github.com/tektoncd/dashboard/issues/1775.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Hi, may I know what to do with this issue? I’ve some free time to work on this issue. :)
This should have been linked to https://github.com/tektoncd/dashboard/issues/1445 which we'll need to tackle first, it was already mentioned above but I've just added it as a blocker now.
There are a number of closely related issues that require us to revisit how we structure and display the Task / step / log details so it all works as users expect without over-complicating the code. You can see some of the discussion in https://github.com/tektoncd/dashboard/issues/1445 and the other linked issues above. Any proposals on this are welcome, and we can discuss them in more detail before implementation.
freezing this so it doesn't get auto-closed since this is something we do want to add
/lifecycle frozen
@AlanGreene Any update on this one ? We will need to do that too, and not sure how Tekton Dashboard is going to handle that.
@shinji62 Currently it's still blocking by #1445. I've worked on color on that issue but I've no time to look it more on that issue at the moment.