Closed Bug 466498 Opened 11 years ago Closed 11 years ago

Need a way to trigger l10n builds for buildbot

Categories

(Release Engineering :: General, defect, P3)

x86
All
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: coop, Unassigned)

Details

(Whiteboard: [l10n])

We currently need to trigger a new round of nightly en-US builds before the dependent l10n scheduler will fire. We should be able to trigger individual (or batch) l10n repacks using the current, existing en-US nightly. 

This might take the form of an extension to the Force Build interface with an extra parameter for locale(s).
Could we use the NightlyL10n scheduler without setting an specific hour?
You can always add the parameter "locales" to the scheduler to tigger a subset if needed.

Another way would be to be able to use sendchange with parameters with a subset of locales or with the word "all" if needed
(In reply to comment #1)
> Could we use the NightlyL10n scheduler without setting an specific hour?
> You can always add the parameter "locales" to the scheduler to tigger a subset
> if needed.
> 

Yes, that's okay-ish. It really sucks that we have to make local changes to the config to do this, though. What I would really love is to be able to use "Rebuild" on a failed build.

> Another way would be to be able to use sendchange with parameters with a subset
> of locales or with the word "all" if needed

I don't think you can pass arbitrary properties to sendchange, but that would be great.
Assignee: nobody → ccooper
Priority: -- → P3
Whiteboard: [l10n]
This is being worked on upstream:

http://buildbot.net/trac/ticket/471
Putting this back in the pool. Hopefully we'll see the upstream fix soon-ish.
Assignee: ccooper → nobody
Component: Release Engineering → Release Engineering: Future
Picked up the upstream change today that allows us to force builds w/ properties from the builder web interface. Need to set locale, en_revision, and l10n_revision, but this looks fixed now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.