job.rst (1741B)
1 Job Transforms 2 ============== 3 4 .. note:: 5 6 These transforms are currently duplicated by standalone Taskgraph 7 and will likely be refactored / removed at a later date. 8 9 A job description says what to run in the task. It is a combination of a 10 ``run`` section and all of the fields from a task description. The run section 11 has a ``using`` property that defines how this task should be run; for example, 12 ``mozharness`` to run a mozharness script, or ``mach`` to run a mach command. 13 The remainder of the run section is specific to the run-using implementation. 14 15 The effect of a job description is to say "run this thing on this worker". The 16 job description must contain enough information about the worker to identify 17 the workerType and the implementation (docker-worker, generic-worker, etc.). 18 Alternatively, job descriptions can specify the ``platforms`` field in 19 conjunction with the ``by-platform`` key to specify multiple workerTypes and 20 implementations. Any other task-description information is passed along 21 verbatim, although it is augmented by the run-using implementation. 22 23 The run-using implementations are all located in 24 ``taskcluster/gecko_taskgraph/transforms/job``, along with the schemas for their 25 implementations. Those well-commented source files are the canonical 26 documentation for what constitutes a job description, and should be considered 27 part of the documentation. 28 29 following ``run-using`` are available 30 31 * ``hazard`` 32 * ``mach`` 33 * ``mozharness`` 34 * ``mozharness-test`` 35 * ``run-task`` 36 * ``spidermonkey`` or ``spidermonkey-package`` 37 * ``debian-package`` 38 * ``ubuntu-package`` 39 * ``toolchain-script`` 40 * ``always-optimized`` 41 * ``fetch-url`` 42 * ``python-test`` 43 * ``gradlew`` 44 * ``run-commands``