Releng is rolling out a new Treestatus, hosted at https://mozilla-releng.net/treestatus/ It should (once some bugs today get fixed) be api-compatible. It's going to forward requests for the old treestatus to the new one, but we should probably just fetch them directly from the new one.
Comment on attachment 8832150 [details] [review] [treeherder] KWierso:newtreestatus > mozilla:master At the moment, canonical Treestatus has been rolled back to the old api.build... version due to some unintended differences in the api response, but the new one should be getting fixed and redeployed soon. So this PR can't get deployed to prod until that happens and sticks.
Attachment #8832150 - Flags: review?(cdawson)
I fixed the API differences, but since it is a bit late I will redeploy new TreeStatus tomorrow 9:00CET.
At this time new TreeStatus is deployed, give it a day before you apply this patch just in case something comes up and we need to rollback the release again).
Attachment #8832150 - Flags: review?(cdawson) → review+
Commit pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/897bb5649b1b03c97e5f5b1da8c9600980f2f181 Bug 1335496 - Use the new Treestatus api (#2120) r=camd
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.