Ticket #2888 enhancement new

Opened 6 years ago

Last modified 10 months ago

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

1

Changed 6 years ago by radix

  • milestone set to twisted-7.0

2

Changed 6 years ago by therve

  • cc therve added

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

3

Changed 6 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.

4

Changed 6 years ago by radix

  • milestone changed from twisted-8.0 to regular-releases

5

Changed 5 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.

6

Changed 4 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.

7

Changed 4 years ago by jml

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

8

Changed 3 years ago by <automation>

  • owner radix deleted

9

Changed 10 months ago by therve

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

10

Changed 10 months ago by tom.prince

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

11

Changed 10 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.