1296771 - If you're viewing jobs by signature, "Add new jobs" doesn't list the job.

Status: RESOLVED WONTFIX

(Tree Management :: Treeherder, defect)

Description

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

If I'm looking at something like https://treeherder.mozilla.org/#/jobs?repo=autoland&fromchange=2544cfc9473e5b66d2e9b7692a34d9f167174c37&bugfiler&filter-tier=1&noautoclassify&filter-searchStr=370930263f22ebb7bf347501a969dc802f81588a&tochange=3da4d64410c002418eab4b025dfb24a6f4f57fd6 to show all of the mn-e10s jobs on osx 10.10 debug, clicking "Add new jobs" on a push does not show me the mn-e10s job on 10.10 debug for that push as an option to trigger.


If I filter instead by the job name like https://treeherder.mozilla.org/#/jobs?repo=autoland&fromchange=2544cfc9473e5b66d2e9b7692a34d9f167174c37&bugfiler&filter-tier=1&noautoclassify&filter-searchStr=10.%20debug%20mn-e10s&tochange=3da4d64410c002418eab4b025dfb24a6f4f57fd6 I get the expected results when I click "Add new jobs".

Is there some way to get them listed when filtered by job signature?

Comment 1

[Cameron Dawson [:camd]]

Yeah, this would involve including the ``reference_data_signature`` in the runnable_jobs.  So I think it's just the API would need to be updated.  Once it's returned in the job JSON that came back from the runnable_jobs API, then it would be used for the filtering and show when appropriate.

Comment 2

[Cameron Dawson [:camd]]

This is still happening.  We would need to modify the endpoint to fetch the appropriate signature for each of the jobs.  This would slow down the endpoint to some degree.  Hard to say how much.  Not sure it's worth it, tbh.

If you use the link to the right of the "sig" link, you will filter by all the text fields.  It's very nearly as accurate.  And this DOES work with add new jobs.  

I'm going to close this as wontfix for now, but if someone considers this an important feature, please reopen and ping me.