Closed
Bug 1319189
Opened 8 years ago
Closed 8 years ago
Create tasks that move desktop l10n artifacts to the s3 final locations
Categories
(Firefox Build System :: Task Configuration, task)
Firefox Build System
Task Configuration
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Assigned: Callek)
References
Details
Attachments
(2 files)
Similar to what we do for the actual beetmover desktop product, we need to do this for l10n.
What we'll do is pass an optional 'locale' as part of the beetmover payload, to indicate its for an l10n task.
We'll create 1 beetmover task per locale.
Assignee | ||
Comment 1•8 years ago
|
||
This is explicitly excluding android for now, since we don't have balrog_props.json generated for android just yet.
Attachment #8812903 -
Flags: feedback?(kmoir)
Comment 2•8 years ago
|
||
Is there a patch I need to review that actually adds these jobs?
Flags: needinfo?(bugspam.Callek)
Comment hidden (mozreview-request) |
Assignee | ||
Comment 4•8 years ago
|
||
(In reply to Kim Moir [:kmoir] from comment #2)
> Is there a patch I need to review that actually adds these jobs?
yes, it'd help if I typed `y` on my mozreview prompt.
Flags: needinfo?(bugspam.Callek)
Comment 5•8 years ago
|
||
mozreview-review |
Comment on attachment 8812908 [details]
Bug 1319189 - Create tasks that move desktop l10n artifacts to the s3 final locations.
https://reviewboard.mozilla.org/r/94456/#review94752
There is extra whitespace in taskcluster/taskgraph/transforms/task.py line 312
Attachment #8812908 -
Flags: review?(kmoir) → review+
Comment 6•8 years ago
|
||
mozreview-review |
Comment on attachment 8812908 [details]
Bug 1319189 - Create tasks that move desktop l10n artifacts to the s3 final locations.
https://reviewboard.mozilla.org/r/94456/#review94754
Assignee | ||
Comment 7•8 years ago
|
||
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Attachment #8812903 -
Flags: feedback?(kmoir) → feedback+
Updated•7 years ago
|
Product: TaskCluster → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•