and then we provide a standard Docker environment ...
# pex
r
and then we provide a standard Docker environment for those builds that only have our “base” libraries
g
This would be 💯 as a built-in, to execute the build inside a given container, and even a layer to make it easy to run inside Kubernetes.
r
noting that the Docker image is for our wheelbuilder tool, not pants itself. so it’s more akin to a “pip install for the monorepo” that just puts prebuilt wheels in the right place for pants to consume. this helps obviate an entire host of at-build-time issues that can pop up when building sdists etc.
👍 1
containerization is also not a solved problem for OSX, so we do our best and just build those locally on dev laptops
g
Agreed, the docker filesystem is sloooooooooooooow
r
longer term, we’re looking at remoting to solve the cross-platform build problem
but Docker + an emphasis on consumption of only bdists in the build has been a boon for our wheelbuilds/third party management
👍 1