Closed
Bug 1076682
Opened 10 years ago
Closed 7 years ago
treeherder: Add all TC artifacts directly to treeherder artifacts
Categories
(Taskcluster :: Services, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jlal, Unassigned)
References
Details
Taskcluster has first class support for artifacts and treeherder also has the same for displaying them... We just need to listen to the artifact exchange and publish them to treeherder jobs as results come in (there may be races?)
Reporter | ||
Updated•10 years ago
|
Assignee: nobody → jlal
Comment 1•10 years ago
|
||
Regarding races, taskcluster-treeherder has prefetch 1 to avoid any races:
https://github.com/taskcluster/taskcluster-treeherder/blob/4f05ac58387d1a0df6d1789211e4d4d371502ae7/treeherder/handlers.js#L57
So we're hopefully not going to have race conditions, but we might eventually have performance issues.
If this turns out to be an actual problem, we do some tricks like prefetching more and queue messages from the
same taskId, so that different taskIds can be treated in parallel.
We'll have race conditions if we try to scale taskcluster-treeherder beyond a single heroku node.
At that point maybe we should just ask treeherder to consume our AMQP messages directly.
Updated•9 years ago
|
Component: TaskCluster → General
Product: Testing → Taskcluster
Updated•9 years ago
|
Assignee: jlal → nobody
Component: General → Integration
Updated•8 years ago
|
Component: Integration → Platform and Services
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•6 years ago
|
Component: Platform and Services → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•