1085659 - Analyse cases where a job isn't ingested due to a null branch/revision in builds-{pending,running,4hr}

Status: RESOLVED WONTFIX

(Tree Management :: Treeherder: Data Ingestion, defect, P4)

Description

[Ed Morley [:emorley]]

As part of job ingestion, if the repo ("branch" in buildbot parlance) or revision isn't set, we skip ingestion of the job.

TBPL did the same, so this isn't a regression, however it would be good to figure out which jobs this is happening for - and if any of them should be fixed (likely in buildbotcustom/buildbot-configs), so they display in Treeherder.

Job types I imagine this will find:
* Release jobs (a la the TBPL bug 609981)
* fuzzer
* l10n

Note there is the related bug 1085649, however that's about jobs that do have both a repo and revision specified, but where the revision is invalid (and so hits the dummy result set handling case, rather than the "let's just skip the job for missing a revision or repo" case).

Comment 1

[Ed Morley [:emorley]]

We've got enough to do without going out of our way to find jobs that are missing attributes. If people don't care enough about their jobs (or validation of builds-* output) then that's their problem.