https://pantsbuild.org/ logo
Join Slack
Powered by
who’s on release duty today? we probably need both...
# development
w
who’s on release duty today? we probably need both a 
2.8.0.dev
and a 
2.7.1rc
looks like this didn’t happen, but i can kick them off today. anyone need anything in?
h
w
🚢
h
When are you envisioning doing dev release? I'd like to land 
./pants tailor
for 
go_binary
, but it's not crucial we do that before
w
h
Oh hm @witty-crayon-22786 can I merge https://github.com/pantsbuild/pants/pull/13210 first? It's green and approved as of 1 minute ago. Internal, so no need to update changelog
w
yep, go ahead. a few things have already landed, so i’m going to update the notes once i get a review.
argh. still locked out of pypi and need to delete more stale releases. tomorrow.
❗ 1
so, i’m going to spend some time today on release automation. but in the meantime, @happy-kitchen-89482: can you run a few more 
pypi-cleanup
commands?
👍 1
for example, seeing how many are matched by 
pypi-cleanup -u $USER -p pantsbuild.pants.testutil -n -r '1\..*dev[0-9]+'
and then running it for real?
h
Ah I will do so
Done
Should I delete v1 rcs too?
w
@happy-kitchen-89482: i think maybe continue with some more contrib packages
before going after rcs
h
Do these all come out of the same storage allowance?
w
… good question. i didn’t think about that.
Copy code
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>
dang.
you’re right. so maybe we do need to try and find more for 
pantsbuild.pants
.
i’m currently working on a prompt for the release process that would suggest exactly which artifacts to delete
…but it looks like on 
pantsbuild.pants
, we only have post-
2.0
rcs
that we can clean up at this point… which starts to get scary.
❗ 1
(and some dev releases, but not many.)
given that we’re so close to the limit even with relatively few 
dev
releases left, i think that we need to actually request more storage.
h
That does get scary...and where do we go in six months? Maybe it's time to consider donating to PyPI to exceed 20gb?
coke
w
@happy-kitchen-89482: the easiest way i’ve found to list everything is:
Copy code
curl '<https://pypi.org/pypi/pantsbuild.pants/json>' | jq . > releases.json
i’ll open the ticket about the limit increase to get the ball rolling there.
@happy-kitchen-89482: did you see anything you can delete? maybe 
2.1.0.dev
and 
2.2.0.dev
releases?
h
Looking
meanwhile I'm deleting dev releases from all the v1 contribs, for good citizenship
w
yea, thank you.
i’m proceeding with this script. it should at least automate suggesting what to delete.
h
Deleted 2.1 and 2.2 dev releases
w
thank you! will finish 
2.8.0.dev4
now.
h
And also literally hundreds of dev releases in v1 contribs
➕ 1
For good citizenship, it doesn't alas help us today
w
@hundreds-father-404: ok, both 
2.8.0.dev4
and 
2.7.1rc1
are out, and need M1 wheels
👍 1
Open in Slack
PreviousNext
Powered by