Closed
Bug 458623
Opened 17 years ago
Closed 17 years ago
update comm-central l10n.ini's for l10n dashboard builds
Categories
(Thunderbird :: Build Config, defect)
Thunderbird
Build Config
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: Pike)
Details
Attachments
(2 files)
1.28 KB,
patch
|
kairo
:
review+
gozer
:
review+
|
Details | Diff | Splinter Review |
2.04 KB,
patch
|
Pike
:
review-
|
Details | Diff | Splinter Review |
I have code in stock to get the buildbot details from l10n.ini. It doesn't require changes to compare-locales, just to the setup of the builds.
Attachment #341842 -
Flags: review?(kairo)
Attachment #341842 -
Flags: review?(gozer)
![]() |
Assignee | |
Updated•17 years ago
|
Assignee: nobody → l10n
Status: NEW → ASSIGNED
![]() |
||
Comment 1•17 years ago
|
||
Axel, someone with Calendar build experience (probably ause) should look over the calendar changes. Please ask him for review as well.
It would also helpful, to understand why these changes are actually necessary. Is there a corresponding bug report for mozilla-central that we could look into to get more background information?
![]() |
Assignee | |
Comment 2•17 years ago
|
||
It adds details about multi-repo builds to l10n.ini. I guess that gozer is really the guy to review this, as he set up an l10n buildbot for comm-central.
There is no example in mozilla-central, as that's only a single-repo build, so the whole problem doesn't exist.
![]() |
||
Comment 3•17 years ago
|
||
Axel, can you show me the code changes to the l10n dashboard stuff that enabled this ? Also, I'd have to find a way to test this change before it goes in.
![]() |
Assignee | |
Comment 4•17 years ago
|
||
It's a chicken-and-egg problem. You can't test the dashboard without the changes to l10n.ini, and you can't test l10n.ini without the changes to the dashboard.
The remaining problem is that I'd rather not push more or less broken code to my public tooling repo.
![]() |
||
Updated•17 years ago
|
Attachment #341842 -
Flags: review?(kairo) → review+
![]() |
||
Comment 5•17 years ago
|
||
Comment on attachment 341842 [details] [diff] [review]
add toolkit and reporter detail info to l10n.ini for included l10n.inis
r=me, though I'd welcome if we could obsolete the [includes] section and replace it with this scheme.
And perhaps this scheme would even enable us to deal with optionally localized extensions in the future, by specifying the path to a locales list (all-locales) and only include checking, etc. if the given locale is listed there.
Both those ideas are followup fodder though.
![]() |
||
Comment 6•17 years ago
|
||
Comment on attachment 341842 [details] [diff] [review]
add toolkit and reporter detail info to l10n.ini for included l10n.inis
I've been able to test that this change doesn't cause horrible build failures in my local builds, so it's probably safe enough for the tip. Once in, Axel, I'd like to see that tooling patches you are sitting on so I can test them out in our l10n dashboard setup.
Attachment #341842 -
Flags: review?(gozer) → review+
![]() |
Assignee | |
Comment 7•17 years ago
|
||
Thanks for the reviews, http://hg.mozilla.org/comm-central/rev/21dfb8bb59fb is the landing on comm-central.
http://hg.mozilla.org/users/axel_mozilla.com/tooling/pushloghtml?fromchange=3c6a3cbe4f44&tochange=37f106027499 are the landings to the buildbot logic.
And http://l10n.mozilla.org/dashboard/ is showing Thunderbird results, and waiting for landings and forces to show seamonkey and calendar, too.
Hope you like that :-)
![]() |
Assignee | |
Comment 8•17 years ago
|
||
Marking FIXED. Not sure about the follow up fodder that KaiRo mentioned.
The current solution has the benefit that it doesn't need a change in compare-locales at all. I'd not aggressively remove the includes section for that reason.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
![]() |
||
Comment 9•17 years ago
|
||
Axel, sure, I didn't want to suggest you're removing includes right now, I just think those things should probably filed as followups.
![]() |
||
Comment 10•17 years ago
|
||
Works great! I backed out my changes, updated, and it almost worked out of the box. I am still running python 2.4, so this includes a little backport of defaultdict. With it, all of it works fine in Python 2.4
Attachment #342246 -
Flags: review?
Comment 11•17 years ago
|
||
Comment on attachment 342246 [details] [diff] [review]
backport defaultdict to python 2.4
gozer, who do you ask for review? ;-)
![]() |
||
Comment 12•17 years ago
|
||
Comment on attachment 342246 [details] [diff] [review]
backport defaultdict to python 2.4
Oh, probably meant it to be Pike, unless you are interested in reviewing it ?
Attachment #342246 -
Flags: review? → review?(l10n)
![]() |
Assignee | |
Comment 13•17 years ago
|
||
Comment on attachment 342246 [details] [diff] [review]
backport defaultdict to python 2.4
Is this still needed?
![]() |
Assignee | |
Comment 14•17 years ago
|
||
Comment on attachment 342246 [details] [diff] [review]
backport defaultdict to python 2.4
Doesn't sound like this is still needed, r-.
Attachment #342246 -
Flags: review?(l10n) → review-
You need to log in
before you can comment on or make changes to this bug.
Description
•