Bug 1539242 - Update link to properties to task definitions in taskcluster's how-to documentation. r=dustin DONTBUILD
authorSebastian Hengst <archaeopteryx@coole-files.de>
Tue, 26 Mar 2019 12:28:02 +0100
changeset 466337 d9aeff28c11b6866a4ade5868364301652a2c8f1
parent 466336 b726b5df4b57284f42ffa08782f5af7724471b3d
child 466338 f9c865b93ecd4d184b50de9a5ca9da15928c27a8
push id35764
push useraciure@mozilla.com
push dateWed, 27 Mar 2019 16:35:35 +0000
treeherdermozilla-central@16f19322ec76 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersdustin
bugs1539242
milestone68.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1539242 - Update link to properties to task definitions in taskcluster's how-to documentation. r=dustin DONTBUILD Differential Revision: https://phabricator.services.mozilla.com/D24949
taskcluster/docs/how-tos.rst
--- a/taskcluster/docs/how-tos.rst
+++ b/taskcluster/docs/how-tos.rst
@@ -81,17 +81,17 @@ platform.  For example:
 .. code-block:: yaml
 
     chunks:
         by-test-platform:
             linux64/debug: 10
             default: 8
 
 The full set of available properties is in
-``taskcluster/taskgraph/transform/tests/test_description.py``.  Some other
+``taskcluster/taskgraph/transforms/tests.py``.  Some other
 commonly-modified properties are ``max-run-time`` (useful if tests are being
 killed for exceeding maxRunTime) and ``treeherder-symbol``.
 
 .. note::
 
     Android tests are also chunked at the mozharness level, so you will need to
     modify the relevant mozharness config, as well.
 
@@ -99,17 +99,17 @@ Adding a Test Suite
 ...................
 
 To add a new test suite, you will need to know the proper mozharness invocation
 for that suite, and which kind it fits into (consult :doc:`kinds`).
 
 Add a new stanza to ``taskcluster/ci/<kind>/tests.yml``, copying from the other
 stanzas in that file.  The meanings should be clear, but authoritative
 documentation is in
-``taskcluster/taskgraph/transform/tests/test_description.py`` should you need
+``taskcluster/taskgraph/transforms/tests.py`` should you need
 it.  The stanza name is the name by which the test will be referenced in try
 syntax.
 
 Add your new test to a test set in ``test-sets.yml`` in the same directory.  If
 the test should only run on a limited set of platforms, you may need to define
 a new test set and reference that from the appropriate platforms in
 ``test-platforms.yml``.  If you do so, include some helpful comments in
 ``test-sets.yml`` for the next person.