Bug 1394054: include try_task_config.json in sparse checkout; r?gps
MozReview-Commit-ID: 5H5XH1Zpqw1
--- a/build/docs/sparse.rst
+++ b/build/docs/sparse.rst
@@ -98,17 +98,17 @@ attribute in YAML (or in code) to denote
use. e.g.::
run:
using: run-command
command: <command>
sparse-profile: tasgraph
This automagically results in ``run-task`` and ``hg robustcheckout``
-using the sparse profile defined in ``build/sparse/profiles/<value>``.
+using the sparse profile defined in ``build/sparse-profiles/<value>``.
Pros and Cons of Sparse Checkouts
=================================
The benefits of sparse checkout are that it makes the repository appear
to be smaller. This means:
* Less time performing working directory operations -> faster version
--- a/build/sparse-profiles/taskgraph
+++ b/build/sparse-profiles/taskgraph
@@ -14,11 +14,14 @@ path:mobile/locales/l10n-changesets.json
path:taskcluster/
# Various files in these directories are read by taskgraph. Just pull
# them all in.
path:testing/config/tooltool-manifests/
path:testing/mozharness/
path:tools/lint/
+# for new-style try pushes
+path:try_task_config.json
+
# Tooltool manifests also need to be opened. Assume they
# are all somewhere in "tooltool-manifests" directories.
glob:**/tooltool-manifests/**