Confirmed users
1,989
edits
ReleaseEngineering:TestingTechniques: Difference between revisions
Jump to navigation
Jump to search
→Taskcluster
| Line 5: | Line 5: | ||
= Taskcluster = | = Taskcluster = | ||
* The | ==Testing changes to the decision task== | ||
* From http://gecko.readthedocs.io/en/latest/taskcluster/taskcluster/taskgraph.html | |||
"The decision task is the first task created when a new graph begins. It is responsible for creating the rest of the task graph. | |||
The decision task for pushes is defined in-tree, in .taskcluster.yml. That task description invokes mach taskcluster decision with some metadata about the push. That mach command determines the optimized task graph, then calls the TaskCluster API to create the tasks. | |||
Note that this mach command is not designed to be invoked directly by humans. Instead, use the mach commands described below, supplying parameters.yml from a recent decision task. These commands allow testing everything the decision task does except the command-line processing and the queue.createTask calls." | |||
[Taskcluster | https://docs.taskcluster.net/] creates a large graph of tasks, some which depend on each other. Each task has different properties. Depending on the code tree that the task runs on, different tasks may run. This decision task will vary depending on the code tree it is running on. | |||
* For every push to a code tree, a Gecko Decision Task runs which generates several files associated with it | * For every push to a code tree, a Gecko Decision Task runs which generates several files associated with it | ||