Skip to content
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

Dropdown to filter tasks in pipeline run #3861

Open
coillteoir opened this issue Dec 29, 2024 · 2 comments
Open

Dropdown to filter tasks in pipeline run #3861

coillteoir opened this issue Dec 29, 2024 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@coillteoir
Copy link

Feature request

A dropdown to filter tasks by status (Completed, Running, Error) in pipeline runs.

Use case

When troubleshooting pipeline failures, it can be difficult to identify where large pipelines are failing, or if a pipeline is hanging it can be useful to quickly filter by running tasks.

@coillteoir coillteoir added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 29, 2024
@AlanGreene
Copy link
Member

Thanks for the feature request @coillteoir. Can you share some more details about the pipelines you're working with? Could you provide some example resources or even screenshots / recording to illustrate the problem?

Some of the types of information that would be useful to help understand your use case:

  • how many pipeline tasks are there in these pipelines?
  • are you using matrix / when expressions?
    • if so, how?
  • are there particular groups / categories within the tasks that should be treated a certain way?
  • are there some tasks that are of more interest than others if they fail?
  • etc.

We're planning some major changes to the TaskRun and PipelineRun details pages as a follow-up to #3768 early in 2025 so now is a good time to consider other capabilities and use cases.

@coillteoir
Copy link
Author

coillteoir commented Dec 31, 2024

Thanks for the quick response,
Currently my organization uses pipelines which are approx 10 pipeline tasks, with some going up to 30+.

We use a large finally block for auto reporting failures to different monitoring platforms (these are grouped together using when expressions).

With the larger pipelines, different tasks can be grouped together based on what sort of functionality they have.

The use case that a filtering system would bring is being able to:

  1. Drill down into failing pipeline tasks specifically. On smaller displays, large pipelines can't be easily parsed.
  2. Show different pipeline task groups by naming semantics, or by labels.
  3. Show the dependencies of a failing task run (tasks with run after configured)

I understand that there are plans to move to a tree view #675, so this filtering may be more complicated (perhaps showing the path to the failing/filtered tasks).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants