We currently can only trigger it if the Scheduler is triggered since it passes the "locales" property. We can change that and we should do it.
Putting back into the pool.
Depends on: 525327
Assignee: armenzg → nobody
Status: ASSIGNED → NEW
Component: Release Engineering → Release Engineering: Future
So the problem here is that you can only specify single-value parameters via the web interface rather than an array of locales?
That is correct.
I'd like for it to be able to check whether it has a locales property, and if not, read its locales in from maemo-locales. However, I'm not entirely certain how this will work with our current addStep-per-locale format.
Mass move of bugs from Release Engineering:Future -> Release Engineering. See http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Whiteboard: [mobile][automation] → [mobile][automation][l10n]
This is a side effect of bug 525327 and will be solved when that's fixed. Duping.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 525327
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.