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
jobs: fix k8s.io deploy jobs #21954
jobs: fix k8s.io deploy jobs #21954
Conversation
was an experiment to see if pod-utils supported cloning HEAD, they do not
specifically - trim post-k8sio-groups to pick up all changes under groups (code changes or configs other than groups.yaml) - trim post-k8sio-deploy-prow* to pick up all changes for prow clusters, not just changes to their resources
fall back to old behavior if the script isn't present
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
/cc @ameukam |
/lgtm |
@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. |
ref: kubernetes/k8s.io#460 for triggering the groups jobs on more than groups.yaml |
Main motivation was to fix the fact that the post-k8sio-groups job didn't trigger when a change to groups/committee-product-security/groups.yaml was merged (ref: kubernetes/k8s.io#1973 (comment))
However I took care of a few other things while I was here: