#11614 Manage pantsbuild.pants release size on PyPI Issue created by jsirois We just hit a 20GB limit with the 2.4.0.dev0 release.

HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/

Project size too large. Limit for project 'pantsbuild.pants' total size is 20 GB. See https://pypi.org/help/#project-size-limit

I worked around this by deleting the 5 dev releases in the 1.16.0 series, which is the 1st series where we started chewing up a bunch of space with several rust wheels per release. I then:

(twine) ^jsirois@gill ~/dev/pantsbuild/pants/dist/deploy/wheels/pantsbuild.pants/b2fbce097ab9f13cfaf710488f813cdf5aeadde4/2.4.0.dev0 (master) $ rm *.asc
(twine) ^jsirois@gill ~/dev/pantsbuild/pants/dist/deploy/wheels/pantsbuild.pants/b2fbce097ab9f13cfaf710488f813cdf5aeadde4/2.4.0.dev0 (master) $ twine upload --skip-existing -s *.whl
Uploading distributions to <https://upload.pypi.org/legacy/>
Signing pantsbuild.pants-2.4.0.dev0-cp37-cp37m-macosx_10_11_x86_64.whl
Signing pantsbuild.pants-2.4.0.dev0-cp37-cp37m-manylinux2014_x86_64.whl
Signing pantsbuild.pants-2.4.0.dev0-cp38-cp38-macosx_10_11_x86_64.whl
Signing pantsbuild.pants-2.4.0.dev0-cp38-cp38-manylinux2014_x86_64.whl
Signing pantsbuild.pants.testutil-2.4.0.dev0-py37.py38-none-any.whl
  Skipping pantsbuild.pants-2.4.0.dev0-cp37-cp37m-macosx_10_11_x86_64.whl because it appears to already exist
  Skipping pantsbuild.pants-2.4.0.dev0-cp37-cp37m-manylinux2014_x86_64.whl because it appears to already exist
  Skipping pantsbuild.pants-2.4.0.dev0-cp38-cp38-macosx_10_11_x86_64.whl because it appears to already exist
Uploading pantsbuild.pants-2.4.0.dev0-cp38-cp38-manylinux2014_x86_64.whl
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 39.4M/39.4M [01:00<00:00, 679kB/s]
Uploading pantsbuild.pants.testutil-2.4.0.dev0-py37.py38-none-any.whl
100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 23.5k/23.5k [00:02<00:00, 9.83kB/s]

View at:
<https://pypi.org/project/pantsbuild.pants/2.4.0.dev0/>
<https://pypi.org/project/pantsbuild.pants.testutil/2.4.0.dev0/>

We need to come up with a strategy for managing our release storage consumption over time as well as come up with a short term plan for freeing up space used by existing releases. As an initial idea it seems to make sense to me to: 1. Delete all .devX releases for all time prior to 2.4.0.dev0 2. Establish a (presumably automated) procedure for deleting all prior dev releases when a new dev series starts. pantsbuild/pants