Closed
Bug 1225220
Opened 9 years ago
Closed 9 years ago
[Raptor] Submit to Treeherder's API using Hawk credentials
Categories
(Firefox OS Graveyard :: Gaia::PerformanceTest, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rwood, Assigned: rwood)
Details
(Whiteboard: [systemsfe])
I have created a treeherder client id named 'raptor' on both staging and production.
Comment 1•9 years ago
|
||
I've authorised that client_id on both the prod and stage instances.
If you point to where the current oauth submission code is, I can assist with migration :-)
Updated•9 years ago
|
Flags: needinfo?(rwood)
Assignee | ||
Comment 2•9 years ago
|
||
Thanks Ed! There was no existing submission code for Raptor, but I am working on it now. Whimboo pointed me to some mozmill-ci treeherder submission code, I have taken that and am currently modifying it for Raptor (I'm not done yet but here it is so far):
https://github.com/rwood-moz/raptor-post
Flags: needinfo?(rwood)
Comment 3•9 years ago
|
||
Ah - bug 1212936 is working out who is left to switch from the EOL oauth credentials to the new Hawk credentials, so we know when we can rip out the old code. Since Raptor isn't submitting at all yet, this bug doesn't need to block bug 1212936.
I'll leave the credentials I approved in comment 1 as-is, but ordinarily we'd wait until the submissions were looking ok against stage before authorising the credentials for prod, so do double check that you're submitting to stage and things look ok before also doing so against prod :-)
No longer blocks: 1212936
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → rwood
Status: NEW → ASSIGNED
Updated•9 years ago
|
Whiteboard: [systemsfe]
Assignee | ||
Comment 4•9 years ago
|
||
Update: Raptor coldlaunch test is now reporting to treeherder staging. Need to fix the test duration shown in treeherder when click on one of the coldlaunch apps, and add support for the reboot test.
Assignee | ||
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•