Build wheels using new single image workflow #3525
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Up until now wheel builds have been using a two-pass, Docker-in-Docker approach that involves having one container run cibuildwheel, which in turn launches a manylinux container in which the build occurs. This approach is cumbersome to work with and makes it difficult to create local builds that match CI exactly. This PR updates to using the new single-image workflow in rapidsai/shared-workflows#71 that uses a new set of Docker images built just for RAPIDS and eschews cibuildwheel in favor of launching
pip wheel
directly. This approach should be far easier to make maintain and make work locally. It also removes our dependence on modifying upstream pypa manylinux images, which is fairly difficult to maintain.