Alice, could you please tackle this with similar priority as pulse_actions? We need a way to determine which jobs have been coalesced for a revision and be able to trigger them. I'm tracking this through bugzilla so we can clearly block bug 1173822 The revision to be considered does not have to be one on which periodic tasks have been triggered.

This might become our first feature running in pulse_actions as a production service (we might use this before even using cancel/retrigger features).

adusca fixed this and we've released it: http://armenzg.blogspot.ca/2015/06/mozci-080-new-feature-trigger-coalesced.html

Mozci gets a list of every job from Buildapi and then uses builds-4hr.js to determine the status of those jobs. For this bug, we had to check the status of every single job on a given revision and we noticed that sometimes the job was not in builds-4hr.js. One cause of this is the job ending. It seems that when a job finishes, it disappears from builds-4hr.js and it reappears again after 1/2 minutes.