1031238 - Switch Treeherder from builds-4hr to Pulse

Status: RESOLVED WONTFIX

(Tree Management :: Treeherder: Data Ingestion, enhancement, P5)

Description

[Ed Morley [:emorley]]

This is very much a longer term goal, but filing before I forget.

Adding the dependant bugs I've found so far, but there will be more.

We'll need to:
1) Ensure that Pulse contains all the properties we use from builds-4hr.
2) Ensure Pulse is reliable enough/on IT managed infra.
3) Update the Treeherder data ingestion process to use Pulse rather than builds-4hr.

Comment 1

[Ed Morley [:emorley]]

I think there are going to be two approaches with this bug:
1) Try to use pulse like we do builds-{pending,running,4hr} at present (ie regexing the buildername).
2) Trying to supplement the pulse output, such that more of the platform name/job name logic is upstream.

I think #2 is too much to do at the moment (and is what some of the deps here are trying to achieve).

However, #1 isn't going to be as straightforwards as "just switching over", since (as I understand it from jeads) there are properties available in builds-{pending,running,4hr} that are not present in pulse.

It seems to me, that until we figure out what those differences are (sadly they were never recorded back then), we're not going to be able to accurately scope the size of this work, or get any traction towards completing it - particularly for the parts that require releng help, and thus advanced notice to get it on their roadmap/goals list.

I'll file a dependent bug for performing the pulse vs builds-{pending,running,4hr} analysis.

Comment 2

[Ed Morley [:emorley]]

I think switching to Pulse is unlikely at this point before buildbot goes away.