#17992 Should we stop building wheels for every commit in main? New discussion created by benjyw Currently we build Pants wheels for every (non-docs) commit in main. This is so people can use PANTS_SHA to easily run Pants at any such commit. However this seems to be used only rarely in practice, and is very costly in CI resources, especially on self-hosted runners. The wheel build shards take almost an hour, on each of 5 target platforms (in large part because we have no effective Rust caching). So we're burning a lot of trees to build and store wheels that will almost certainly never be used. And meanwhile PR CI runs can be delayed waiting for resources to free up. I propose that we only build wheels when we need them for a release. If someone needs to run at a SHA, we give clear guidance on how to build those wheels as needed. pantsbuild/pants