-
Notifications
You must be signed in to change notification settings - Fork 592
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
Eventing.yaml missing for 0.17 #3873
Comments
The upgrade test is failing because of the missing file. |
This is the prow job that created the release. I can see that it created the YAML file:
And then inspected it:
It appears to have attempted to upload
|
It looks like
Oddly enough, we seem to generate the same YAML for both 0.16 and 0.17 post-release jobs. Trying to figure out:
|
I don't think [[ -s ${artifact} ]] || abort "Artifact ${artifact} is empty" And we don't see the error line. |
Questions from above:
|
I think this is caused by having the same file being uploaded twice. The first upload succeeds. The second fails with
So removing the old post-install job should allow |
v0.17.0 is a bad release, see knative#3873. It is blocking any new PRs and is blocking the creation of a new release because the bad release is being used in the upgrade test, causing it to fail.
v0.17.0 is a bad release, see #3873. It is blocking any new PRs and is blocking the creation of a new release because the bad release is being used in the upgrade test, causing it to fail.
|
@pierDipi: 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. |
Describe the bug
While the script still has it:
https://github.com/knative/eventing/blob/master/hack/release.sh#L33
we do not have a release asset
eventing.yaml
for our 0.17 release, see:https://github.com/knative/eventing/releases
Expected behavior
a convenient
eventing.yaml
file is there for downloadThe text was updated successfully, but these errors were encountered: