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

Configured Tests Dashboard #208

Open
petr-muller opened this issue Jul 11, 2024 · 1 comment
Open

Configured Tests Dashboard #208

petr-muller opened this issue Jul 11, 2024 · 1 comment

Comments

@petr-muller
Copy link
Contributor

Migrated kubernetes/test-infra#28979

What would you like to be added:
A new dashboard that lists all configured jobs in the Prow instance. It should be filterable by org and repo. It should show a prettified view of the yaml for the job. It should also link to the job-history page for each respective job.

Why is this needed:
Test maintainers need an easy way to see all of the jobs configured for a specific org or repo.
There are a few issues with existing methods for seeing jobs:

  • Looking through the config files isn't a good user experience
  • Job-History is not easily navigable, and doesn't provide a list view
  • Deck only shows jobs that have executed very recently

msugakov commented Oct 4, 2023:

I needed something like this to compare jobs and configs set up for different branches of the project. I ended up creating a script that spits out an HTML page that's checked in along the configs and can be viewed online courtesy to Refined GitHub. Not sure how much are my needs specific to ci-operator, though.

@BenTheElder
Copy link
Member

Worth noting: some prow instances (like prow.k8s.io) have a TON of jobs and this might be expensive to render.
FWIW users can find presubmits by commenting /test and the robot will reply with a full list.

Maybe a page that fetches the config endpoint and then allows you to filter by job type and repo and renders that subset?

Deck only shows jobs that have executed very recently

Dependent on your sinker config. We keep ~24h or most recent execution in prow.k8s.io, though I've been thinking about if we might need to reduce this because it's a ton.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants