I've floated around the idea of adding a link to the buildbot step which would be a link to a URL on the perf dashboard which would start a bisect. It would be prefilled with information about the build. I'm not sure if that's the nicest solution, but it would work and give us a mechanism to start bisects fairly easily.

Simon and Dave can comment on how to best kick off a pinpoint job from sheriff-o-matic.

I think you might also want to check with FindIt team, to see if they have any type of integration that checks WHEN to kick off a (bisect|flake analysis).

Dashboard already treats Pinpoint as a separate thing and communicates via Pinpoint's api. You can find examples here:

https://github.com/catapult-project/catapult/blob/master/dashboard/dashboard/pinpoint_request.py
https://github.com/catapult-project/catapult/blob/master/dashboard/dashboard/services/pinpoint_service.py

Keep in mind that it's not 100% stable yet, since Dashboard is really the only client and we change to suit needs (although almost always it's just adding more params to plumb through for additional functionality). I'd be happy to help or sit down to go through all the params though.

You'll also need a service account: https://github.com/catapult-project/catapult/blob/master/dashboard/dashboard/api/examples/service_account.py

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot