rpm builds are piling up in latest-* directories on stage

RESOLVED FIXED

Status

Release Engineering
General
P3
normal
RESOLVED FIXED
7 years ago
5 years ago

People

(Reporter: coop, Assigned: jhford)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [rpm][cleanup])

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
Because our rpms include the build id in the filename, they don't simply overwrite the current rpm in the latest dirs on stage. 

e.g.

http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/

It looks like the files get purged eventually when they hit the global retention threshold, but we should really only have one rpm per linux arch in each latest dir.

My preference here would be to strip the build id out of the rpm filename for the copy going to latest. That could probably be done using post_upload.py.

We'll also need to clean out the older rpm files from all the latest-* dirs on stage.
(Reporter)

Updated

7 years ago
Priority: -- → P3
Created attachment 541863 [details] [diff] [review]
fixit

I don't even care if they end up in latest-$branch.  I guess I could have that pref go all the way to the platform dict in config.py, but I don't think that is worthwhile.
Attachment #541863 - Flags: review?(coop)
(Reporter)

Comment 2

7 years ago
Comment on attachment 541863 [details] [diff] [review]
fixit

I'm personally fine with this change, given that the rpms are meant to be consumed via the repo. John, you'll need to monitor for feedback on this to see if community members have started relying on having rpms under latest-* though.

Oh, and don't forget to clean up the existing rpms from the latest-* dirs.
Attachment #541863 - Flags: review?(coop) → review+
Depends on: 667910
(In reply to comment #2)
> Comment on attachment 541863 [details] [diff] [review] [review]
> fixit
> 
> I'm personally fine with this change, given that the rpms are meant to be
> consumed via the repo. John, you'll need to monitor for feedback on this to
> see if community members have started relying on having rpms under latest-*
> though.

Ok, filed bug 667910 to figure out how many people have downloaded these files

> Oh, and don't forget to clean up the existing rpms from the latest-* dirs.

Will do!
Done.  Cleaned up straggling June 28 rpms in the process.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.