Add symlink from revision sha1 to timestamp directory for ftp.mozilla.org builds

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
4 years ago
5 months ago

People

(Reporter: nalexander, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

I would like a symlink from, for example:

http://ftp.mozilla.org/pub/mozilla.org/mobile/tinderbox-builds/fx-team-android-api-11/a803874de085

to

http://ftp.mozilla.org/pub/mozilla.org/mobile/tinderbox-builds/fx-team-android-api-11/1423618318

My use case is going from a local commit to a pushlog entry and then to build artifacts.  Right now I need to manually open treeherder, view the appropriate sha1, choose the appropriate build artifact, and manually copy the build directory timestamp to download artifacts.  I talked to camd who assures me that there exists a build API for extracting this data, but it's complicated and this is simple.  (If not future proof: eventually these build artifacts will move to S3.)
13:41 <~bhearsum> nalexander: part of the reason for that is to cope with rebuilds
13:41 <~bhearsum> if you based it on push time, rebuilds would overwrite each other
13:41 <~bhearsum> which gets confusing
13:42 < nalexander> bhearsum: oh, that's a good note.  Could you add it to the ticket?
13:42 <@catlee> also nightlies
13:42 <@catlee> or pgo builds
13:42 <@catlee> or other periodic builds

That's not to say there isn't other ways of coping with this. Eg, for releases we directories like http://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/36.0b8-candidates/, which have "build1", "build2", etc. inside of them. I'm not sure if that would work for this case, considering that nightly+pgo+periodic+dep could overwrite each other without any rebuilds.
Component: Release Automation → General Automation
QA Contact: bhearsum → catlee

Updated

2 years ago
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
(Assignee)

Updated

5 months ago
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.