Jul 8, 2016, 9:49:49 AM7/8/16
to Cameron Dawson, tools-taskcluster, dev-pl...@lists.mozilla.org, dev-tree-...@lists.mozilla.org, tools-tr...@lists.mozilla.org
As a follow up, I would like to point out a couple of pieces of information:
mozilla-taskcluster is still operational for scheduling decision tasks and
handling actions from treeherder (cancel/retrigger) for taskcluster tasks.
Only api submission for jobs was turned off and now handled by our new
component, taskcluster-treeherder . At some point the remaining
functionality will be split into separate services leading to the
decomission of mozilla-taskcluster.
Taskcluster tasks have always contained data under task.extra.treeherder,
but now we have a schema  published that this data is validated against
and can also be used as a reference.
A new field, 'jobKind', has been added to this section. This allows a task
to declare what type of task it is and Treeherder can take actions
appropriate for the kind of task that's being reported. Currently the most
notable difference is when a task marked as 'build' fails, it will be
reported to Treeherder as red. Previously all job failures were reported
orange (testfail) regardless of the job type. Failed tasks with a jobKind
of test will be reported as orange and any task which does not specify
jobKind or is marked as 'other' will be shown as red.
We made sure that all existing tasks that are being reported could pass
this validation and in the future we will work with task
creators/maintainers at adding more validation constraints for this data.
> dev-tree-management mailing list