Change FTP scraper to look for betas and releases in candidates/ instead of nightly/

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
6 years ago
6 years ago

People

(Reporter: kairo, Assigned: rhelmer)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
Bug 725839 changed build automation to put beta and release candidates into candidates/ instead of nightly/ and we probably should change the Socorro FTP scraper to do the same. The good news with that is that it makes Firefox, Thunderbird, and SeaMonkey have the same structure as Fennec there. Right now we have symlinks in nightly/ so our stuff still works, but those might not be there forever.

jhopkins, this applies to Firefox and Thunderbird the same, right?

Callek, adding you as well here as SeaMonkey is affected as well (I know it now uses candidates/ just as the others, so just FYI).
Robert: yes, Thunderbird and Firefox automation works the same with respect to symlinks on stage.
(Assignee)

Updated

6 years ago
Assignee: nobody → rhelmer
Status: NEW → ASSIGNED
(Assignee)

Comment 2

6 years ago
The ftpscraper code actually already looks in both nightly and candidates dirs for betas and releases. It would save some time if we didn't have to look in the nightly dir, but I am not sure when it'll be safe to remove support.

Are older releases going to be coped/symlinked into the candidates dir?
(Reporter)

Comment 3

6 years ago
(In reply to Robert Helmer [:rhelmer] from comment #2)
> The ftpscraper code actually already looks in both nightly and candidates
> dirs for betas and releases. It would save some time if we didn't have to
> look in the nightly dir, but I am not sure when it'll be safe to remove
> support.

OK, and having the same release show up in both is also not breaking anything?

> Are older releases going to be coped/symlinked into the candidates dir?

Not sure, leaving that to jhopkins. :)
> Are older releases going to be coped/symlinked into the candidates dir?
> Not sure, leaving that to jhopkins. :)

Can you please file a separate Release Engineering bug to track that request?  As I understand it, the bug I worked on (bug 725839) does not cover that work.
(Assignee)

Comment 5

6 years ago
(In reply to John Hopkins (:jhopkins) from comment #4)
> > Are older releases going to be coped/symlinked into the candidates dir?
> > Not sure, leaving that to jhopkins. :)
> 
> Can you please file a separate Release Engineering bug to track that
> request?  As I understand it, the bug I worked on (bug 725839) does not
> cover that work.

It's not really important, if the answer is "no" that just means I need to leave the fallback code in place until all of the current releases expire, which is fine :)
(Assignee)

Updated

6 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.