Create base MacOS CI pipeline #360
Conversation
|
From the checks this appears to be good to go. You can auto-apply formatting fixes with |
| with: | ||
| path: ./wheelhouse/*.whl | ||
|
|
||
| - name: Publish package |
There was a problem hiding this comment.
It seems like the preferred way of doing this is to have a separate workflow with the on: release trigger.
There was a problem hiding this comment.
I know it's possible to share data between jobs but how is it possible to persist built wheels between workflows?
There was a problem hiding this comment.
Instead of persisting the wheel between workflows, we can just rebuild the wheel in the release workflow. (I usually cut releases via the Github API, which IIUC separates the "release" and "push" events.)
There was a problem hiding this comment.
Yeah, that makes sense, I opened a new PR with the changes #379
| # The Kokoro MacOS VMs are not configured for AVX2 or OpenMP, so these modes | ||
| # are excluded from the build and test process. |
There was a problem hiding this comment.
Update comments to refer to Github Actions, rather than Kokoro.
This PR addresses a cross-platform wheels issue and adds support for building and uploading MacOS wheels for
cp36, cp37, cp38, cp39onx86_64architecture.