Automating test-infra release branch job forking

18 views
Skip to first unread message

Katharine Berry

unread,
May 3, 2019, 2:51:30 PM5/3/19
to kubernetes-...@googlegroups.com
Hi sig-release,

I am working on tooling to automate the manual config juggling currently performed by the release team test-infra role. The gist of the automation is that at branch cut time, a tool will generate a single file per release containing all the branch-specific jobs for that release.

There are two visible results of this:

- Instead of using jobs named {beta, stable1, stable2, stable3}, the jobs will instead be named after the branch they're for (e.g. {1-14, 1-13, 1-12, 1-11}). The original beta/stable naming scheme was to make it easier to handle the updates, but that didn't work out as well as was hoped.
- Because there is only one output file, only one set of OWNERS can apply. I think that these OWNERS should be sig-release. This does not imply that sig-release is responsible for fixing the jobs if they break, only that they (or sig-testing) need to stamp any changes made to the release-branch jobs.

You can see some more discussion of this on the GitHub PR introducing the tool: https://github.com/kubernetes/test-infra/pull/12443

Let me know if you have any feedback.

Thanks!
-- Katharine

Tim Pepper

unread,
May 3, 2019, 4:24:29 PM5/3/19
to Katharine Berry, kubernetes-...@googlegroups.com

From: 'Katharine Berry' via kubernetes-sig-release <kubernetes-...@googlegroups.com>
Reply-To: Katharine Berry <kt...@google.com>
Date: Friday, May 3, 2019 at 11:51 AM
>

>

> (e.g. {1-14, 1-13, 1-12, 1-11})

 

 

Hallelujah!!!

Aaron Crickenberger

unread,
May 7, 2019, 5:05:25 PM5/7/19
to kubernetes-sig-release
I'm going to assume given the lack of objections on this thread that we are clear to proceed with this plan.  I'm reviewing https://github.com/kubernetes/test-infra/pull/12516 before any other testgrid or job-related PRs to try and avoid rebase fun

- aaron

Stephen Augustus

unread,
May 7, 2019, 5:43:29 PM5/7/19
to Aaron Crickenberger, kubernetes-sig-release
Explicit +1. Thanks y'all!

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
To post to this group, send email to kubernetes-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-release/3316d591-0607-48d3-9a97-59ae7fe3c95d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Tim Pepper

unread,
May 7, 2019, 6:02:31 PM5/7/19
to Stephen Augustus, Aaron Crickenberger, kubernetes-sig-release

Explicit +1 from me too.

 

-- 

Tim Pepper

Orchestration & Containers Lead

VMware Open Source Technology Center

Reply all
Reply to author
Forward
0 new messages