-
Notifications
You must be signed in to change notification settings - Fork 65
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
Update cryptonono's location #3613
Conversation
Merging this PR will trigger the following deployment actions. Support and Staging deployments
Production deploymentsNo production hub upgrades will be triggered |
Ha, maybe a premature approval there :D |
Hmm, is there any caching happening? I see it trying to fetch the chart from the original location still:
|
From the error message, I think it's still trying to pull the old repo. So it may be a "merge and hope" scenario, due to how the repo is getting checked out in CI. |
Does it work locally? I'm not sure that we cache anything helm chart related in CI. I think it's likely running as if on master and not executing the change |
We may also want to consider this PR https://github.com/2i2c-org/infrastructure/pull/3482/files |
Hmm, I just checked and same happens locally 🤔 |
This website is a 404 https://cryptnono.github.io/cryptnono/ |
Seems the repo is still trying to deploy to https://yuvipanda.github.io/cryptnono but that is now also a 404 https://github.com/cryptnono/cryptnono/deployments/github-pages |
I opened an issue cryptnono/cryptnono#26 |
I believe that is acceptable, but https://cryptnono.github.io/cryptnono/cryptnono-0.3.1-0.dev.git.107.heb504bc.tgz has appropriate resource.
So maybe the workflows need updating? |
But that's what this PR is doing, which leads me back to my original assumption that we hit merge and hope? In the sense that it's something funky about what context GitHub Actions is running the workflow on. It will be running the version of the workflow that's in master on the changes in this PR. ETA: Sorry, realised you may have meant on the cryptnono repo, not here |
Sorry, I moved it for this blog post (2i2c-org/2i2c-org.github.io#205) but somehow thought github will also do redirects for the generated gh-pages stuff (not just the repo). I'm going to merge this to unblock folks. |
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/7504949158 |
So this is failing on the main branch as well :( I've opened cryptnono/cryptnono#28 but not sure if that's enough to fix things? |
cryptnono/cryptnono#27 and cryptnono/cryptnono#29 seem to have fixed it. |
Yaay! 🚀 |
The repo has moved under a new account: https://github.com/cryptnono/cryptnono (see cryptnono/cryptnono#25 (comment))