Open Bug 1496858 Opened 7 years ago Updated 6 years ago

Explore improving how we get access to the gecko decision task id

Categories

(Tree Management :: Treeherder: Frontend, enhancement, P3)

Product:
Tree Management
Component:
Treeherder: Frontend
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: camd, Unassigned)

References

Details

Attachments

(1 file)

Link to GitHub pull-request: https://github.com/mozilla/treeherder/pull/4858
47 bytes, text/x-github-pull-request
Details | Review
Right now we go and find the job in the list of jobs for that push, then we have to download the detailed job to get some taskcluster_metadata that has the info we need for retriggers, etc. It might be good to streamline this and get that metadata for that job per-push right away. Maybe the /jobs/ endpoint could add the necessary fields by default? Not sure yet what the right answer is, but want to explore this later.
Blocks: treeherder-react
Priority: -- → P3
No longer blocks: treeherder-react
See Also: → 1523848
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: