-
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
config/tests/jobs: add check for use of k8s-release-dev bucket #19871
config/tests/jobs: add check for use of k8s-release-dev bucket #19871
Conversation
enforce that anything extracting from ci/latest-fast should be using the k8s-release-dev bucket drop ci/latest-fast from skew job; I would prefer it use latest-fast, but ci/stable1 hasn't migrated over yet, and extract-ci-bucket applies to all extracts
FYI @kubernetes/ci-signal |
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.
thanks for that Aaron
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, spiffxp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@spiffxp: Updated the
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. |
enforce that anything extracting from ci/latest-fast should be
using the k8s-release-dev bucket
drop ci/latest-fast from skew job; I would prefer it use latest-fast,
but ci/stable1 hasn't migrated over yet, and extract-ci-bucket applies
to all extracts
This should close out #19484
but I'll do that manually after looking things over