You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
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.
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:
msugakov commented Oct 4, 2023:
The text was updated successfully, but these errors were encountered: