Marco Castelluccio

> I'm looking into this and have a few questions: > > * there already exists [firefox source code checkouts](https://firefox-source-docs.mozilla.org/taskcluster/caches.html#version-control-caches) in Taskcluster cache, but they are restricted to tasks ran...

Regarding the integration hook, I think it has been broken for a while. It would be useful to have it working again, though it's not a huge priority.

We already listen for task failures, so we'd need to check if a task failure corresponds to one of the revisions we pushed and report a failure if it does...

> This second one wouldn't work for you, because you wouldn't have the push_id shown here as 616255. So I'll need to create a summary endpoint that just takes a...

@camd thanks! What about: > Is there a way to get the health per task instead of the whole push?

I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1607265 for that.

> The Treeherder main UI uses this to get a summary : https://treeherder.mozilla.org/api/project/autoland/push/616255/health_summary/ This is now something like: https://treeherder.mozilla.org/api/project/try/push/health_summary/?revision=92d62183d7b415aa43b274681cd6aa2848abe1e9

I'm not sure how far we want to go here, we might prefer just relying on Treeherder for details.

@armenzg @camd for build failures, we are adding a bit of detail to the failures. See for example the part which reads: ``` Code review bot found a build error:...

@armenzg how do I know the job ID for a given task? I'm listening for task-completed, so I have the following information at my disposal: ``` { "status": { "taskId":...