Opened 7 years ago

Last modified 15 months ago

#2888 enhancement new

Automate uploading release tarballs

Reported by: radix Owned by:
Priority: normal Milestone: totally automated release infrastructure
Component: release management Keywords:
Cc: therve Branch:
Author: Launchpad Bug:

Description

Do this please.

Change History (11)

comment:1 Changed 7 years ago by radix

  • Milestone set to twisted-7.0

comment:2 Changed 7 years ago by therve

  • Cc therve added

Do you know how to make the upload? Is it ssh, sftp, ftp?

comment:3 Changed 7 years ago by radix

Actually, we only have to get the files to cube. There's a cronjob that runs to rsync the files from cube to the mirrors. So we can sftp them to cube.

comment:4 Changed 7 years ago by radix

  • Milestone changed from twisted-8.0 to regular-releases

comment:5 Changed 6 years ago by radix

I should mention that TMRC isn't really important here; the important thing is to automate the uploading of the tarballs to *somewhere* publicly accessible. This is an important distinction because there are other file services with easy-to-use APIs which we could use for file hosting.

comment:6 Changed 5 years ago by jml

FWIW, automatically uploading the tarballs to cube right now involves uploading to cube:/srv/www-data/twisted/Releases/<Project>/<First two parts of version number>/*. The directories need to be created, and the permissions need to be set correctly.

New directories are 2775, and ought to be in the www-data group. New files are 664, and ought to be in the www-data group.

comment:7 Changed 5 years ago by jml

We might also want to automate signing the tarballs / msis and uploading the signatures.

comment:8 Changed 4 years ago by <automation>

  • Owner radix deleted

comment:9 Changed 15 months ago by therve

  • Summary changed from Automate uploading tarballs to TMRC to Automate uploading release tarballs

comment:10 Changed 15 months ago by tom.prince

There is some code in braid to do this. I'm not sure how this should be integrated.

comment:11 Changed 15 months ago by exarkun

It seems like this should build on the work done for #4353. Using one tool to upload pre-release packages and another tool to upload release packages doesn't seem like a good goal to aim for.

Note: See TracTickets for help on using tickets.