Closed Bug 588746 Opened 14 years ago Closed 8 years ago

Fake l10n repack builder as part of regular depend builds

Categories

(Release Engineering :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: Pike, Unassigned)

References

(Depends on 1 open bug)

Details

(Whiteboard: [automation][l10n][tryserver])

Given that we're busting l10n nightlies for the second time in a row, we should have a test.

Something like a triggered build like the tests, with a fake partial locale and an l10n-merge build reporting to the regular tinderbox would be useful, obviously.

Not sure if we can test release code paths, too, or if nightly and l10n dep need separate tests, depends a good deal on how shared their factories are these days.
I don't think testing release paths make sense here -- we don't test any other release paths for on-change builds. Testing an l10n build makes a lot of sense though. If we set it up to trigger x-testing only, would that be good enough?
I'd prefer us to be independent of x-testing, as that's good to have as an independent playground.

Re release code path, I'm never sure what variable we exactly pass in, thus I'd prefer to have a test for it.
OK, but I don't think we should be publishing real updates to any locale for this. Could we create a new fake locale for it?
Priority: -- → P3
Whiteboard: [automation][l10n]
Depends on: 525438
We'll be getting our summer intern Nick to start looking into adding this to Try (and then to other branches as needed).
Whiteboard: [automation][l10n] → [automation][l10n][tryserver]
(In reply to comment #5)
> We'll be getting our summer intern Nick to start looking into adding this to
> Try (and then to other branches as needed).

Sorry I never got back round to this bug until now to update. We didn't end up getting that intern, so this project did not start and at present I can't give a good estimate of when it might be tackled.  It will stay attached to try_enhancements tracking so that at least it won't drop completely off my radar. That's the best I can say for now.
Product: mozilla.org → Release Engineering
Is this useful in the face of l10n-check?
Flags: needinfo?(l10n)
I think so. Maybe more so if we're doing this with a pseudo localization similar to what we doing for gaia in bug 900182.

CCing glandium and gps, as they're the folks suffering from lack of testability of l10n automation mostly these days, I think.
Flags: needinfo?(l10n)
Component: Other → General Automation
QA Contact: catlee
:Pike if this bug was solved with 'real' locales (eg. en-GB, ru, ja-jp[-mac], zh-CN, etc) would there still be value for a "fake" locale, if so who/what controls said "fake" locale, would it be in tree/generated from in tree or something?
Flags: needinfo?(l10n)
I think this is good to dupe on the real locales at this point.
Flags: needinfo?(l10n)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.