Closed Bug 1353673 Opened 7 years ago Closed 2 years ago

Run creation cross-channel localization repository in automation

Categories

(Firefox Build System :: Task Configuration, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Pike, Unassigned)

References

(Depends on 1 open bug)

Details

Once we have the code pieces to create the generated en-US repository for cross-channel localization (see dependent bugs, probably more to come), we'll want to automate that creation.

Filing this in taskcluster, because I think we'd want this to be a tc job.

We'd want this job to run on changes to mozilla-central and comm-central, and branches thereof, with the code for the job being in version-control-tools.

I think it'd be good if the result of the job was on treeherder as part of the regular tier-1 builds, but we might also have a job-specific result queue.
I'm assuming this is somehting you can work on?
Assignee: nobody → l10n
The actual workload is something I can/will do, but I expect to need a good amount of help with wiring things up in taskcluster and to get the results formed such that they show up treeherder.

Things to figure out that I know so far: First comm-central job to be on taskcluster. Running a job on, then, beta, with configuration coming from central. Even comm-beta and mozilla-central, perhaps. Which of that is a good fit is also something to figure out.

The rationale for why I'd like to have configuration in the m-c repo is that the config is global for all branches, and I see value to have the configuration changes land as part of the merge day process. 'cause then we don't have to synchronize landings across various people landing stufff on various repositories.

The project configuration piece is a bug list that's still to be filed, too, I'll hook up dependencies here. It'd be good to get some comments on pre-existing and proven ways, though, to inform the decisions in those bugs.
Assignee: l10n → nobody
Depends on: 1384901
Axel, is this still a thing?  I'd like to keep un-actionable, un-owned bugs out of this component.
Flags: needinfo?(l10n)
Yes. Right now, we're dog-fooding the code that will run in automation on local machines, but we will automate that later this quarter.
Flags: needinfo?(l10n)
Product: TaskCluster → Firefox Build System

This has been running in automation for a while (bug 1659691).

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.