bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

Figure out how to pass MAR URLs to l10n partial generator

RESOLVED FIXED

Status

Release Engineering
Release Automation: Other
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: rail, Assigned: rail)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

3 years ago
When we generate a release promotion graph, we don't yet know the final URLs of complete MARs generated by desktop_l10n.py.

We have the following options to define these URLs:

1) Use FTP, err, S3 URLs based on pre-defined URL pattern, something like 
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2015/10/2015-10-11-06-35-47-date-l10n/firefox-44.0.gu-IN.linux-i686.complete.mar

pros: relatively easy to implement, doesn't require AUTH, the URL is predefined
cons: hard coded URLs are bad

2) Use TC Index to calculate the corresponding task IDs and then use them to retrieve the corresponding artifacts:
Something like:
 * GET https://index.taskcluster.net/v1/task/gecko.v2.date.revision.a9320053068dd168603884e5e3b1062d193fd048.firefox-l10n.linux-opt.he
 * use taskId to generate the URL *run time* https://queue.taskcluster.net/v1/task/CqawVj44RW2GtM5_icXgLw/runs/0/artifacts/public/build/firefox-44.0.he.linux-i686.complete.mar

Pros: relatively easy to implement, uses TC artifacts
Cons: requires buildbot2treeherder platform conversion (we can add another route to fix this)
(Assignee)

Updated

3 years ago
Depends on: 1216152
(Assignee)

Updated

3 years ago
Assignee: nobody → rail
(Assignee)

Comment 1

3 years ago
Done Done Done
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.