Closed
Bug 1404010
Opened 7 years ago
Closed 7 years ago
Extend the worker to have the runId of its most recentTask
Categories
(Taskcluster :: Services, enhancement)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hassan, Assigned: hassan)
References
Details
Presently, when a user is on the workers page, clicking on the most recent task id will take you to the latest run of that task. What we want is to link the user to the actual runId of that task. To implement that, we need to:
- Extend the queue API to return the runId of the most recent task
- Add logic in the tools website to link the user to that /groups/${taskGroupId}/tasks/${taskId}/runs/${runId}
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → helfi92
Assignee | ||
Updated•7 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•7 years ago
|
||
On azure, we're storing the the list of most recent task ids in `recentTasks`. The problem with this is that it's currently stored as a SlugIdArray. This is a problem because we can't include the runId to it. To that end, I will need to switch the data type of the `recentTasks` azure property to a JSON blob to be a list of the most recent (taskId, runId).
Comment 2•7 years ago
|
||
Good point let's make it:
recentTasks: [{taskId: '...', runId: ...}, ...]
Comment 3•7 years ago
|
||
Commit pushed to master at https://github.com/taskcluster/taskcluster-queue
https://github.com/taskcluster/taskcluster-queue/commit/01a517db767074f60b21fe6411ed46f1124f6b10
Merge pull request #210 from helfi92/extend-worker-to-have-runid
Bug 1404010 - Extend the worker to have the runId of its most recentTask
Assignee | ||
Updated•7 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: Queue → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•