Conversation
|
This is great, it will be very nice to I recently went through the PyPI process on another project, and I found a useful testing workflow is to set up an account on https://test.pypi.org/, configure the CI job to use the TestPyPI instance, and then make releases on a forked repo to see that the CI job runs successfully when it's supposed to and that wheels appear on TestPyPI. It's useful to test everything out since there's a lot to juggle: PyPI secret keys, GitHub actions YAML, wheel files... Once everything is validated, change the workflow to point to the real PyPI instance and merge. |
|
@kylc Thanks! Starting with test.pypi.org seems prudent - @zkingston or @mamoll, do you think we could make an account there to start testing? |
|
I think we can close this, since I already added this in separate commits. |
Thanks to @kylc's work in #1103, we now have consistently building OMPL Python wheels. The next step for
pip-installable OMPL, I think, is to get these wheels automatically deploying to PyPI.This PR adapts the basic upload action example from the
cibuildwheeldocs for this purpose. It seems pretty straightforward, but I'm not very experienced with GH Actions, so we should verify that I've not missed anything.There are two (that I know of) outlying tasks:
Then, we should be able to cut a new release, and see the wheels upload.