Add support for new l10n jobs on try

RESOLVED FIXED

Status

P2
normal
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: nthomas, Assigned: emorley)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Bug 848284 is adding some desktop l10n builders on try:
 Firefox try linux l10n
 Firefox try linux64 l10n
 Firefox try macosx64 l10n
 Firefox try win32 l10n
 Firefox try win64 l10n
which are showing up as '?' on https://treeherder.mozilla.org/#/jobs?repo=try&revision=6c4d51201ce1

We run similar jobs on m-c and m-a, except they have a -N suffix like this
 Firefox mozilla-central linux l10n nightly-1. 

Could we adjust the regexps to put the new try builds into an L() ?
(Assignee)

Updated

3 years ago
Assignee: nobody → emorley
Component: Treeherder → Treeherder: Data Ingestion
Priority: -- → P2
(Assignee)

Comment 1

3 years ago
Thank you for listing the buildernames :-)

There exists an L10n() group at the moment, should these jobs be added to that?
Presumably they should be displayed as something like:

L10n(B1 B2 B3 ...) ?
(Assignee)

Updated

3 years ago
Flags: needinfo?(nthomas)
(Reporter)

Comment 2

3 years ago
Just L10n(B) would be fine, there's no chunking being used here.
Flags: needinfo?(nthomas)
Created attachment 8748132 [details] [review]
[treeherder] mozilla:support-new-l10n-jobs > mozilla:master
(Assignee)

Comment 4

3 years ago
Comment on attachment 8748132 [details] [review]
[treeherder] mozilla:support-new-l10n-jobs > mozilla:master

The symbol ended up being L10n for consistency with the other non-nightly repack job. I can change this if preferred, I'll just need to rejog a few of the regexes. (Roll on the day when we can throw away this whole file haha)
Attachment #8748132 - Flags: review?(nthomas)
(Reporter)

Comment 5

3 years ago
Comment on attachment 8748132 [details] [review]
[treeherder] mozilla:support-new-l10n-jobs > mozilla:master

lgtm!
Attachment #8748132 - Flags: review?(nthomas) → review+
(Assignee)

Updated

3 years ago
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.