976691 - Update b2g cronjobs to keep the next 12 weeks worth of builds after 3/17's merge day

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Armen [:armenzg]]

On bug 974571, we started keeping the last 12 weeks' worth of hamachi builds.

See https://bugzilla.mozilla.org/show_bug.cgi?id=969767#c45 for summary.

This bug will require some prep work to figure out what exactly has to change.

I believe this bug will help deal with nthomas' concern:
> What's left is to figure how we're handling things on the next merge. From
> reading [1] we will also care about mozilla-aurora-hamachi* after March 17
> (for 1.4), and some b2g-inbound & mozilla-central dirs for the reference
> device.
> 
> [1]
> https://wiki.mozilla.org/ReleaseEngineering/Merge_Duty/
> Central_will_become_an_odd_numbered_Gecko_version

Comment 1

[Rail Aliiev [:rail]]

Attachment: [productdelivery] b2gbld cron

Comment 2

[Armen [:armenzg]]

IIUC the goal in here is to:
* add a 12 week retention policy for the hamachi aurora builds
* add a 12 week retention policy for the TBD device(s) for mozilla-central/b2g-inbound

This is not a rush type of bug but we need to move before the default retention policy removes the TBD device builds. I assume that is Tarako or the Flame once we start publishing them.

Is this right?

rail's patch (from what I read) deals with #1.
We will need a second patch once we publish the TBD device.

To summarize what the current state is afaik:
Up until 3/17 we have keep 12 weeks' worth of b2g-inbound/mozilla-central Hamachi builds.
We have Hamachi builds as far as the 11th of February for FF30 (when they were added). After May 11th we will start loosing those builds one day at a time.

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 8392845 [details] [diff] [review]
[productdelivery] b2gbld cron

This looks fine to save the aurora hamachi builds.

For the future, the branches are going to change purpose a lot, so I've been wondering if we should set up something like 
 ..../b2gotoro/tinderbox-builds/1.4/
which contains all the relevant builds. We'd have the dirs b2g-inbound-hamachi* and so on under that, to cope with integration branches (otherwise I'd just make it flat by buildID). Using hardlinks would prevent blowing out a space requirement, while preserving existing locations. Or maybe we don't even need the latter if we take a 'mental paradigm shift to embrace synergistic opportunities.', and just upload into the versioned location.

Comment 4

[Rail Aliiev [:rail]]

Comment on attachment 8392845 [details] [diff] [review]
[productdelivery] b2gbld cron

$ svn commit -m "Bug 976691 - Update b2g cronjobs to keep the next 12 weeks worth of builds after 3/17's merge day. r=nthomas"    
Sending        files/cron/b2gbld
Transmitting file data .
Committed revision 84921.