Taskcluster: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(out of date warning....)
(Update the basic details about taskcluster)
Line 1: Line 1:
'''Everything is out of date''', see [http://docs.taskcluster.net docs.taskcluster.net] for information about the current project.
= TaskCluster =
= TaskCluster =


== Description ==
== Description ==


TaskCluster is the name for a new task execution framework on to which we intend to move our test CI system.  A "task" will typically be a test job, but could be other things as well.  Initially, TaskCluster will power the Gaia Shepherd project, but will eventually be expanded to run buildbot jobs and perform other kinds of work as well.
Taskcluster is a generic "task" execution service this page documents mostly administrative things such as who owns which components and when the team meets.


== Docs ==
For detailed documentation on the API's and capabilities please see see [http://docs.taskcluster.net docs.taskcluster.net].


* [https://etherpad.mozilla.org/automation-futures automation-futures etherpad]
== Meetings ==


== Status Meetings ==
=== TaskCluster Meeting ===


* [[Auto-tools/Projects/TaskCluster/Meetings]]
When: Tuesday 8am PST
Where: James Lal's Room
Agenda: https://etherpad.mozilla.org/fxos-automation


== Components ==
This meeting is to discuss new ideas/critical issues/etc... This meeting is required for owners
of modules (but open to all) and may be cancelled if there is no Agenda.


=== Job Queue (owner: dminor/ted) ===
=== FxOS Automation Hang Out ===


The job queue accepts requests for tasks to be executed, and interacts with the provisioner and the workers to execute them.
When: Tuesday 8am PST
Where: James Lal's Room


* [https://etherpad.mozilla.org/OAjWjiMC3q job queue etherpad]
Totally arbitrary meeting usually just an hour for people to hack together (completely optional time reserved for calendaring purposes)
* [http://collabedit.com/ukdrh definition of task structure]


=== Provisioner (owner: jonas) ===
== Components ==
 
The provisioner is responsible for creating and destroying workers.
 
* [https://etherpad.mozilla.org/bKjtVtGnCu provisioner API]


=== Worker (owner: lightsofapollo) ===
Our team follows a simple version of the usual "module ownership" pattern seen all over Mozilla... Each owner is responsible for
the health (which is defined as uptime/code quality/decisions) made in each component owned. The ideal is we collaborate through our weekly
meetings but each owner is ultimately responsible for yes/no decisions. Owners are _not_ for life and the team may elect new owners as
time goes on.


The worker is responsible for executing tasks.
This is a list of components which as a whole make up TaskCluster... Please contact the owners and visit the github pages for full context:


* [https://github.com/taskcluster worker components on github]
* [aws-provisioner https://github.com/taskcluster/aws-provisioner] - jhford
* [queue https://github.com/taskcluster/taskcluster-queue] - jonasfj
* [scheduler https://github.com/taskcluster/task-graph-scheduler] - jonasfj
* [auth https://github.com/taskcluster/taskcluster-auth] - jonasfj
* [index https://github.com/taskcluster/taskcluster-index] - jonasfj
* [events https://github.com/taskcluster/taskcluster-events] - jonasfj
* [tools https://github.com/taskcluster/taskcluster-tools] - jonasfj
* [s3-copy-proxy https://github.com/taskcluster/s3-copy-proxy] - james
* [mozilla-taskcluster https://github.com/taskcluster/mozilla-taskcluster] - james
* [docker-worker https://github.com/taskcluster/docker-worker] - garndt
* [generic-worker https://github.com/petemoore/generic-worker] - pmoore
* [taskcluster-client-go https://github.com/petemoore/taskcluster-client-go] - pmoore
* [taskcluster-client-py https://github.com/petemoore/taskcluster-client.py] - jhford
* [taskcluster-cli https://github.com/taskcluster/taskcluster-client] - garndt

Revision as of 21:20, 2 June 2015

TaskCluster

Description

Taskcluster is a generic "task" execution service this page documents mostly administrative things such as who owns which components and when the team meets.

For detailed documentation on the API's and capabilities please see see docs.taskcluster.net.

Meetings

TaskCluster Meeting

When: Tuesday 8am PST Where: James Lal's Room Agenda: https://etherpad.mozilla.org/fxos-automation

This meeting is to discuss new ideas/critical issues/etc... This meeting is required for owners of modules (but open to all) and may be cancelled if there is no Agenda.

FxOS Automation Hang Out

When: Tuesday 8am PST Where: James Lal's Room

Totally arbitrary meeting usually just an hour for people to hack together (completely optional time reserved for calendaring purposes)

Components

Our team follows a simple version of the usual "module ownership" pattern seen all over Mozilla... Each owner is responsible for the health (which is defined as uptime/code quality/decisions) made in each component owned. The ideal is we collaborate through our weekly meetings but each owner is ultimately responsible for yes/no decisions. Owners are _not_ for life and the team may elect new owners as time goes on.

This is a list of components which as a whole make up TaskCluster... Please contact the owners and visit the github pages for full context:

Retrieved from "https://wiki.mozilla.org/index.php?title=Taskcluster&oldid=1078052"