Bug 1347889 - use 'relative-datestamp' instead of typo 'relative-timestamp' in morphs, to unbreak task submission. r=dustin
authorJustin Wood <Callek@gmail.com>
Thu, 16 Mar 2017 09:44:36 -0400
changeset 398440 f4156ce504324d4aa5c4688f640f262d2ba811b7
parent 398439 231a2fc0fe33ab9235afd1909b0a899c66ce8e88
child 398441 d7637cb130548622c567a11d052d84bca58353eb
push id1490
push usermtabara@mozilla.com
push dateMon, 31 Jul 2017 14:08:16 +0000
treeherdermozilla-release@70e32e6bf15e [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersdustin
bugs1347889
milestone55.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 1347889 - use 'relative-datestamp' instead of typo 'relative-timestamp' in morphs, to unbreak task submission. r=dustin MozReview-Commit-ID: 8GCKi6r4WUD
taskcluster/docs/taskgraph.rst
taskcluster/taskgraph/morph.py
--- a/taskcluster/docs/taskgraph.rst
+++ b/taskcluster/docs/taskgraph.rst
@@ -185,17 +185,17 @@ Task Parameterization
 
 A few components of tasks are only known at the very end of the decision task
 -- just before the ``queue.createTask`` call is made.  These are specified
 using simple parameterized values, as follows:
 
 ``{"relative-datestamp": "certain number of seconds/hours/days/years"}``
     Objects of this form will be replaced with an offset from the current time
     just before the ``queue.createTask`` call is made.  For example, an
-    artifact expiration might be specified as ``{"relative-timestamp": "1
+    artifact expiration might be specified as ``{"relative-datestamp": "1
     year"}``.
 
 ``{"task-reference": "string containing <dep-name>"}``
     The task definition may contain "task references" of this form.  These will
     be replaced during the optimization step, with the appropriate taskId for
     the named dependency substituted for ``<dep-name>`` in the string.
     Multiple labels may be substituted in a single string, and ``<<>`` can be
     used to escape a literal ``<``.
--- a/taskcluster/taskgraph/morph.py
+++ b/taskcluster/taskgraph/morph.py
@@ -52,17 +52,17 @@ def derive_misc_task(task, purpose, imag
     # this is why all docker image tasks are included in the target task graph: we
     # need to find them in label_to_taskid, if if nothing else required them
     image_taskid = label_to_taskid['build-docker-image-' + image]
 
     task_def = {
         'provisionerId': 'aws-provisioner-v1',
         'workerType': 'gecko-misc',
         'dependencies': [task.task_id, image_taskid],
-        'created': {'relative-timestamp': '0 seconds'},
+        'created': {'relative-datestamp': '0 seconds'},
         'deadline': task.task['deadline'],
         # no point existing past the parent task's deadline
         'expires': task.task['deadline'],
         'metadata': {
             'name': label,
             'description': '{} for {}'.format(purpose, task.task['metadata']['description']),
             'owner': task.task['metadata']['owner'],
             'source': task.task['metadata']['source'],