-
Notifications
You must be signed in to change notification settings - Fork 827
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
pull-k8sio-cip should fail on manifest changes that mutate tags #1520
Comments
Is this eventually relevant/related to kubernetes-sigs/promo-tools#277? |
/cc |
/milestone v1.21 |
/milestone v1.22 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale |
/assign @listx |
I've begun work on this now. |
kubernetes-sigs/promo-tools#385 has been merged, so this is fixed now. I just need to deploy it to the various Prow jobs that use the promoter. |
Waiting on kubernetes/test-infra#23148 to get merged. |
This should be fixed now, but just for good measure let me try to perform a tag move in a fake promotion PR. |
/milestone v1.23 |
@listx have you verified this is fixed? |
@justaugustus Have we deployed a new version of the promoter that includes the fix from kubernetes-sigs/promo-tools#385 ? |
@listx -- This is still dependent on getting tests passing on the default dry-run PR: kubernetes-sigs/promo-tools#285 |
@justaugustus I see kubernetes-sigs/promo-tools#285 has merged, are we running a version of the promoter that includes this fix now? |
We are indeed! It was rolled out as part of kubernetes/test-infra#23591 (and kubernetes/test-infra#23593). /assign |
From #2738 (comment):
Thanks for the fix, @listx! /close |
@justaugustus: Closing this issue. 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. |
#1509 should not have been allowed to merge
It did, and broke:
pull-k8sio-cip appeared to skip, but not fail, attempted tag moves in dry-run mode: (ref: #1519 (comment))
FYI @kubernetes/release-engineering
The text was updated successfully, but these errors were encountered: