openshift/tektoncd-pipeline-operator

Clear seperation of Tasks within PipelineRun Logs

Closed this issue · 6 comments

An issue I have found when deploying Pipelines with multiple Tasks is when these Tasks include install commands it fills up a large portion of the Logs therefore making it extrememly hard to navigate around.

The Tekton dashboard has a great feature that allows for realtime analysis of PipelineRun and TaskRun logs - (https://github.com/tektoncd/dashboard)

To make this more accessable could I request adding a feature similar to this to help seperate the Logs by Task in later updates? - This would greatly help and debug.

@Homopatrol Are you referring to these steps inside a task is hard to navigate and should have its own tab? or is it something else?

steps

@karthikjeeyar Yes the steps inside the task should have its own tab. This is because the output of one step (for example installing) can take up a large portion of logs which means lots of redundant scrolling through afterwards to find the step you need.

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.