c73a5bb8f8
* eliminate heading for test kinds, of which there is now only one * make the caches document have a single heading in the TOC * break out mach commands into a separate document, add ./mach taskgraph morphed * remove docs for YAML templates support (the .yml file wasn't actually used -- I expect it was a merge leftover); these are still used for actions.yml, but once that is gone the code should be removed, too. * break try out into its own document, edit to distinguish "how to run try" from "how to generate config" MozReview-Commit-ID: 76ZopWA9TPL
35 lines
1.1 KiB
ReStructuredText
35 lines
1.1 KiB
ReStructuredText
.. taskcluster_index:
|
|
|
|
TaskCluster Task-Graph Generation
|
|
=================================
|
|
|
|
The ``taskcluster`` directory contains support for defining the graph of tasks
|
|
that must be executed to build and test the Gecko tree. This is more complex
|
|
than you might suppose! This implementation supports:
|
|
|
|
* A huge array of tasks
|
|
* Different behavior for different repositories
|
|
* "Try" pushes, with special means to select a subset of the graph for execution
|
|
* Optimization -- skipping tasks that have already been performed
|
|
* Extremely flexible generation of a variety of tasks using an approach of
|
|
incrementally transforming job descriptions into task definitions.
|
|
|
|
This section of the documentation describes the process in some detail,
|
|
referring to the source where necessary. If you are reading this with a
|
|
particular goal in mind and would rather avoid becoming a task-graph expert,
|
|
check out the :doc:`how-to section <how-tos>`.
|
|
|
|
.. toctree::
|
|
|
|
taskgraph
|
|
mach
|
|
loading
|
|
transforms
|
|
optimization
|
|
docker-images
|
|
cron
|
|
try
|
|
actions
|
|
how-tos
|
|
reference
|