-
Notifications
You must be signed in to change notification settings - Fork 161
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
Failure to upload to GCS does not prevent a bad GitHub Release #2374
Comments
#1782 is an umbrella issue for Knative release process, which also mentioned this issue. |
This issue is stale because it has been open for 90 days with no |
/lifecycle frozen |
/close |
@chizhg: 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. |
This was found while investigating knative/eventing#3873.
Expected behavior: If (during a release) any asset uploads fail, then the entire release immediately fails.
When a release is being created, assets are uploaded GCS. But nothing seems to check if that upload succeeded. It just blindly assumes that it did. https://github.com/knative/test-infra/blob/master/scripts/release.sh#L65-L70
This caused a bad release, https://github.com/knative/eventing/releases/tag/v0.17.0, because it was missing the final two assets that should have been uploaded.
Logs from the prow job:
The text was updated successfully, but these errors were encountered: