Treeherder's UI was just switched over to using `/push/` in: https://github.com/mozilla/treeherder/pull/4514 Looking at New Relic: https://insights.newrelic.com/accounts/677903/explorer/events?eventType=Transaction&filters=%255B%257B%2522key%2522%253A%2522request%252euri%2522%252C%2522value%2522%253A%2522resultset%2522%252C%2522like%2522%253Atrue%257D%255D&duration=86400000&facet=user_agent ...I see the following third parties are still using `/resultset/`: - mozscreenshots: I've filed https://github.com/mnoorenberghe/mozscreenshots/issues/41 - wpt-sync: I've filed https://github.com/mozilla/wpt-sync/issues/287 (plus some browser user agents, which are presumably from people who've not yet reloaded the page after the PR was deployed) Once those are switched over, and New Relic looked at again to check for any others, it should be safe to remove the `/resultset/` endpoint.
Bug 1437719 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Treeherder's UI was just switched over to using `/push/` in: https://github.com/mozilla/treeherder/pull/4514 Looking at New Relic: https://insights.newrelic.com/accounts/677903/explorer/events?eventType=Transaction&filters=%255B%257B%2522key%2522%253A%2522request%252euri%2522%252C%2522value%2522%253A%2522resultset%2522%252C%2522like%2522%253Atrue%257D%255D&duration=86400000&facet=user_agent ...I see the following third parties are still using `/resultset/`: - mozscreenshots: I've filed https://github.com/mnoorenberghe/mozscreenshots/issues/41 - wpt-sync: I've filed https://github.com/mozilla/wpt-sync/issues/287 (plus some browser user agents, which are presumably from people who've not yet reloaded the page after the PR was deployed) Once those are switched over, and New Relic looked at again to check for any others, it should be safe to remove the `/resultset/` endpoint.