-
Notifications
You must be signed in to change notification settings - Fork 4
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
CircleCI: "Upload Packages" step fails, wheels are not published #67
Comments
Together with @btlogy we could login to PyPi and generate a new token for PyPI - but we don't have access to test.pypi.org yet (https://test.pypi.org/project/python-challenge-bypass-ristretto/) so we first need to get that from the only maintainer |
@btlogy please create an account for publishing on test.PyPI.org and retrieving authorization for publishing for this project ❤️ |
I've created the same |
We should be back in business on test.pypy.org. |
I've triggered a re-run of the master branch on CircleCI... |
All 🟢 |
Wait: green but I do not see any new package released!? |
We still need to add new PyPI API credentials to the CI config, no? |
I think this overview shows nicely what all didn't work: https://github.com/LeastAuthority/python-challenge-bypass-ristretto/runs/33664282092 It looks to me like the name of that workflow doesn't fit so well - it is called 'all tests' yet most of it is about packaging and publishing. The tests report green and then all the publishing doesn't happen :/ |
That's from 2 weeks ago: I've re-run all jobs from the master branch yesterday and it was green. |
They are defined as env. var. in the project settings on CircleCI (always were, but rotated only yesterday). But indeed, the job ends on a successful "Upload Packages" stating:
Ok, I've found the culprit: the variable name in the config differs from the code (only for the test): I've fixed it. And re-run the job, but from the GitHub overview, just to see if the new result will show there too. |
Thanks! Great to have one part completed at least :) |
Regarding deployment: I think we might want to wait with a proper "release" (i.e. making a tag on master) until we have made sure the current failing tests in zkapauthorizer are not due to a regression in python-challenge-bypass-ristretto |
Now that #65 is fixed the builds on master fail again, but now with a different problem (one example CircleCI run).
The "Upload Packages" step fails with:
The text was updated successfully, but these errors were encountered: