1353365 - Add an API endpoint to accept Travis CI webhook notifications

Status: RESOLVED WONTFIX

(Tree Management :: Treeherder: API, enhancement)

Description

[(not currently active) Ted Mielczarek]

Travis CI supports sending notifications to a webhook (see URL). If we added an API endpoint to Treeherder to accept these notifications, we could get build status from projects using Travis CI.

The primary motivation here is that I'd like to get build timings out of Rust/Servo builds into Perfherder, both of which are building in Travis CI, and Perfherder data ingestion happens as part of Treeherder log ingestion, so this seems like the most straightforward way to make it happen.

Alternately, I suppose we could stand up a separate service that accepted Travis notifications via a webhook, translated them and published them as Pulse messages for Treeherder to consume.

Comment 1

[Ed Morley [:emorley]]

15:02 <emorley> the github commit data comes via taskcluster currently, I wonder if it makes more sense to do the same for job data too?
15:03 <emorley> ie run the jobs on travis still, but have the bridge be the taskcluster component not treeherder
15:03 <emorley> otherwise we then have to add two webhooks to every repo

Comment 2

[Ed Morley [:emorley]]

We're wanting to move to a world where Treeherder uses only Pulse for data ingestion (bug 1395337 etc). As such, this would need to be a separate service that translated these to Pulse payloads (the taskcluster service may already do much of this), to reduce complexity on the Treeherder side, plus provide a data ingestion buffer to reduce issues caused by eg Treeherder downtime or API availability.