Closed
Bug 1254679
Opened 8 years ago
Closed 7 years ago
mozilla-taskcluster should use revision_hash returned from the POST to Treeherder /resultset
Categories
(Taskcluster :: Services, defect)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: camd, Unassigned)
References
Details
Treeherder will be changing the value it stores as a revision_hash for resultsets and jobs. But currently, Task Cluster integration relies on having a matching creation algorithm for that value. After bug 1254673 lands, mozilla-taskcluster should use the revision_hash value we return from the POST creation of a new resultset. That endpoint will return the revision_hash regardless of whether the resultset already existed, or was newly created.
Reporter | ||
Comment 1•8 years ago
|
||
Greg: this has been pushed to stage. If things look good on new relic, I'll push it to master in an hour or so. Here's the example response you'll get: {u'message': u'well-formed JSON stored', u'resultsets': [ { u'revision_hash': u'45f8637cb9f78f19cb8463ff174e81756805d8cf', u'long_revision': u'cdfe03e77e66', u'push_timestamp': 1384353511, u'id': 20 } ] } the revision would actually usually be 40 chars. This was just from a sample script I was testing with.
Updated•8 years ago
|
Component: Integration → Platform and Services
Comment 2•7 years ago
|
||
revision_hash is no longer used.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•5 years ago
|
Component: Platform and Services → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•