-
Notifications
You must be signed in to change notification settings - Fork 112
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
Nightly releases failing since 05/18 #788
Comments
Arg, damn, we forgot to check that. @qu1queee can also help with that as he recently added the base-git and git repositories there. |
Updates from my side:
I will try more things now, if I fail, I will need to summon Adam :) |
Ok, so its fixed, see https:/shipwright-io/build/actions/runs/885321531. The problem was that we were missing [1] and [2], and the reason why it was not working after that, is because the bots required "Write" permissions, I add only "Read". @adambkaplan fyi @imjasonh thanks for finding this. |
e.g., https:/shipwright-io/build/runs/2617025110 from 5/19
Relevant logs:
It seems possibly related to #770 (cc @SaschaSchwarze0) which renamed
./cmd/manager
to./cmd/shipwright-build-controller
, and the image it builds fromquay.io/shipwright/shipwright-operator
toquay.io/shipwright/shipwright-build-controller
(which is more correct thank you 🙏 )I think someone has to manually create the quay.io/shipwright/shipwright-build-controller repository in Quay to be able to push manifests there. @adambkaplan does that sound right?
The text was updated successfully, but these errors were encountered: