cncf-infra / infrasnoop

2 stars 0 forks source link

Add prow jobs to infra-snoop #2

Open hh opened 1 year ago

hh commented 1 year ago

We need a json based table of prow job yaml (from the test-infra repo) with a secondary table with data pulled in from the running prow cluster.

Combined we should be able the job-name, job-github-url, job definition data (from within the url, we'll pick as we go), job result data (from the ruling prow instance)

Ideally we can determine job:

Docs for jobs here:

hh commented 1 year ago

@zachmandeville let's merge and iterate here. I'd like to see this deployed as a coder template so @xmundrii and others from #sig-k8s-infra can start exploring.

hh commented 1 year ago

A good MVP would allow the pseudo query:

To track down jobs where the cluster is unset for a specific set of labels:

select job where labels contains 'labelY' and annotations contains `annotationX' and cluster is nil

Or a stretch goal, track down jobs where the cluster is unset for a specific sig:

select job where sig = 'sig-release' and cluster is nil
hh commented 1 year ago

https://github.com/kubernetes/test-infra/blob/048ae841330ecb46bc990714769670c1b040ffcc/config/jobs/kubernetes/sig-release/release-branch-jobs/1.25.yaml#LL140C17-L140C17

This label would allow us to find kind jobs:

  labels:
    preset-dind-enabled: "true"
hh commented 1 year ago

I created an org file https://github.com/cloudnative-coop/space-templates/blob/main/infrasnoop/org/ii.org which is fed to https://coder.ii.nz/templates/infrasnoop/workspace

If we update this with the current workflow, the feedback from @kubermatic will help tweak the infrasnoop db to answer the questions at hand.