466498 - Need a way to trigger l10n builds for buildbot

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[Chris Cooper [:coop] (he/him)]

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).

Comment 1

[Armen [:armenzg]]

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

Comment 2

[Axel Hecht [:Pike]]

http://hg.mozilla.org/users/axel_mozilla.com/tooling/file/b2fc94a2af23/buildbotcustom/buildbotcustom/status/l10n.py#l141 does that for me.

Comment 3

[[e-mail] (:bhearsum)]

(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.

Comment 4

[Chris Cooper [:coop] (he/him)]

This is being worked on upstream:

http://buildbot.net/trac/ticket/471

Comment 5

[Chris Cooper [:coop] (he/him)]

Putting this back in the pool. Hopefully we'll see the upstream fix soon-ish.

Comment 6

[Chris Cooper [:coop] (he/him)]

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.

Comment 7

[Chris Cooper [:coop] (he/him)]

Moving closed Future bugs into Release Engineering in preparation for removing the Future component.