Bug 1380391 - Index decision tasks under pushlog_id draft
authorBrian Stack <bstack@mozilla.com>
Wed, 12 Jul 2017 10:56:02 -0700
changeset 607744 2b3689541c9050909e1dd96e65c85b895702c59b
parent 607669 03bcd6d65af62c5e60a0ab9247ccce43885e707b
child 637134 4f235b8ec84fd790b49477f8dafc1abfc11516b0
push id68096
push userbstack@mozilla.com
push dateWed, 12 Jul 2017 20:12:35 +0000
Bug 1380391 - Index decision tasks under pushlog_id MozReview-Commit-ID: 9q3iHqJ0OSb
--- a/.taskcluster.yml
+++ b/.taskcluster.yml
@@ -58,16 +58,17 @@ tasks:
       workerType: "gecko-decision"
       provisionerId: "aws-provisioner-v1"
         createdForUser: {{owner}}
         - "index.gecko.v2.{{project}}.latest.firefox.decision"
+        - "index.gecko.v2.{{project}}.pushlog-id.{{pushlog_id}}.decision"
         - "tc-treeherder.v2.{{project}}.{{revision}}.{{pushlog_id}}"
         - "tc-treeherder-stage.v2.{{project}}.{{revision}}.{{pushlog_id}}"
         - "notify.email.{{owner}}.on-failed"
         - "notify.email.{{owner}}.on-exception"
           # checkout-gecko uses these to check out the source; the inputs
--- a/taskcluster/docs/cron.rst
+++ b/taskcluster/docs/cron.rst
@@ -22,23 +22,23 @@ hook configured for each repository supp
 runs every 15 minutes, and the resulting task is referred to as a "cron task".
 That cron task runs `./mach taskgraph cron` in a checkout of the Gecko source
 The mach subcommand reads ``.cron.yml``, then consults the current time
 (actually the time the cron task was created, rounded down to the nearest 15
 minutes) and creates tasks for any cron jobs scheduled at that time.
-Each cron job in ``.cron.yml`` specifies a ``job.using``, corresponding to a
+Each cron job in ``.cron.yml`` specifies a ``job.type``, corresponding to a
 function responsible for creating TaskCluster tasks when the job runs.
 Decision Tasks
-For ``job.using`` "decision-task", tasks are created based on
+For ``job.type`` "decision-task", tasks are created based on
 ``.taskcluster.yml`` just like the decision tasks that result from a push to a
 repository.  They run with a distinct ``taskGroupId``, and are free to create
 additional tasks comprising a task graph.
 The cron task runs with the sum of all cron job scopes for the given repo.  For