-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[WIP] releng: Add stable4 and remove beta generated jobs #18169
Conversation
7c94b74
to
63f1ba4
Compare
5fc5fd1
to
634450c
Compare
/assign @BenTheElder @spiffxp @tpepper |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cpanato, hasheddan, justaugustus, markyjackson-taulia, saschagrunert The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold
I have not seen agreement / consensus that 1.16 is getting retroactive 12+ month support. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this leaves things in a state where forked / manually authored jobs (ie: anything current on the sig-release-1.18-blocking/informing dashboards) end in "beta" and the generated jobs end in "stable1" and that seems really confusing to me
@@ -54,7 +54,7 @@ def delete_dead_branch(branch_path, current_version): | |||
|
|||
|
|||
def rotate_files(rotator_bin, branch_path, current_version): | |||
suffixes = ['beta', 'stable1', 'stable2', 'stable3'] | |||
suffixes = ['stable1', 'stable2', 'stable3', 'stable4'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
making this change without making a corresponding change to all of the non-generated jobs with the word 'beta` in them is confusing
latest-{{.Version}} are inherently cross builds, so having the latest-{{.Version}}-cross markers is redundant. (This commit matches another in 18163, so it'll get rebased out of whichever PR lands last.) Signed-off-by: Stephen Augustus <[email protected]>
beta markers shift depending on the stage in the release cycle and can end up being inaccurate without consistent care and feeding of the generated jobs. Here we remove the beta job configs (not the k8s-beta version marker; that'll happen in an upcoming commit) and establish a new 'stable4' version config. This serves a few purposes: - beta releases are now cut from the main ('master') branch, so the 'dev' 'k8sVersions'/'nodeK8sVersions' configs are now sufficient to describe the beta phase of the release cycle - now that we've expanded the support cycle for Kubernetes versions (from 1.19 on) to 12+ months, removing the previous jobs no longer falls neatly in line with the timing of the next branch cut. The 'stable4' job configs will now allow us to maintain generated jobs through the newly extended support cycle. Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
df83e1d
to
7546a75
Compare
Moving this back to WIP, but rebased, so the PR doesn't fall too far behind.
@spiffxp -- While that's true, we have agreed on extended support for 1.19+, which means our test config needs to support that possibility, irrespective of any decisions for retroactively extending support for older branches. Discussion is happening here and we need to close the loop on that: https://kubernetes.slack.com/archives/CDTMPM75W/p1594146739077400 |
@justaugustus: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@justaugustus: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
I'll think through this after the break. |
@justaugustus: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Part of kubernetes/sig-release#850.
(Needed ahead of this week's branch cut.)Remove extraneous
latest-{{.Version}}-cross
markerslatest-{{.Version}}
are inherently cross builds, so having thelatest-{{.Version}}-cross
markers is redundant.(This commit matches another in releng: Publish fast builds to a separate subdirectory #18163, so it'll get rebased out of
whichever PR lands last.)
Drop test config for beta jobs, add stable4 jobs
beta markers shift depending on the stage in the release cycle and can
end up being inaccurate without consistent care and feeding of the
generated jobs.
Here we remove the beta job configs (not the k8s-beta version marker;
that'll happen in an upcoming commit) and establish a new
stable4
version config.
This serves a few purposes:
master
) branch, so thedev
k8sVersions
/nodeK8sVersions
configs are now sufficient todescribe the beta phase of the release cycle
(from 1.19 on) to 12+ months, removing the previous jobs no longer
falls neatly in line with the timing of the next branch cut. The
stable4
job configs will now allow us to maintain generated jobsthrough the newly extended support cycle.
Regenerate jobs
Update dashboard group/tab references
cc: @kubernetes/release-engineering @kubernetes/wg-lts