Test-infra: Migrate jobs from prow/config.yaml to config/jobs/**/*.yaml

[krzyzacy]

Might write a helper script, but big things:

• generated jobs
• k-s/k jobs

/area jobs
/assign

[krzyzacy]

cc @BenTheElder

[spiffxp]

/milestone 1.12

[stevekuznetsov]

@krzyzacy are you breaking this up into multiple pulls? Would be useful to track them here in a checklist

[krzyzacy]

@stevekuznetsov I'm sorta doing it sigs by sigs, I'll add a ref to this issue

[krzyzacy]

@BenTheElder how do we wanna split presubmits? per-sig, or per-branch under a different subdir? (or we should solve the root issue to make them easier to configure? :-) )

[krzyzacy]

also probably cc @spiffxp @fejta @cjwagner @stevekuznetsov ^^ any preferences

[BenTheElder]

config/jobs/kubernetes/kubernetes/sig-foo-presubmits.yaml ?

[krzyzacy]

I feel like it will be easier for us to configure if we do config/jobs/kubernetes/kubernetes/release-1.x-presubmits.yaml, since this will become a job for test-infra lead in release cycles...

[BenTheElder]

I feel like it will be easier for us to configure if we do config/jobs/kubernetes/kubernetes/release-1.x-presubmits.yaml, since this will become a job for test-infra lead in release cycles...

Hmmm. I think these should be organized by sig still. We can grep for release-specific jobs or build some tooling to find them... other than when we go to set up a release these should be sorted by who owns them imho, and we should set up OWNERS

[spiffxp]

We don't have a jobs/kubernetes/kubernetes why would we start for presubmits? eg: jobs/kubernetes/sig-foo/kubernetes-presubmits.yaml?

[krzyzacy]

yeah I'll put them into kubernetes/sig-foo/sig-foo-presubmits.yaml

[BenTheElder]

Hmm. Are sig-foo-presubmits only k/k? As long as they're seperate that's fine with me. I only said k/k in the path to avoid sig-foo-presubmits being a catch all across repos.

[krzyzacy]

yay