Closed
Bug 1178877
Opened 9 years ago
Closed 9 years ago
queue: Implement task.priority
Categories
(Taskcluster :: Services, defect)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jonasfj, Assigned: jonasfj)
References
Details
Attachments
(1 file)
Add support for priority, at this point I suggest we add the following priorities: - normal - high (requires scope: "queue:task-priority:high") well, something like that. We can always add more priority levels, but we shouldn't add them unless we really need them.
Updated•9 years ago
|
Component: TaskCluster → Queue
Product: Testing → Taskcluster
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → jopsen
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•9 years ago
|
||
@garndt, Your worker will be polling from this... It should work -- it's not really different from when we had legacy queue names. Anyways, give it a quick review, and feel free to ask questions :) @jhford, you're the only one who has actually used base.Entity migration in production. Is there anything I should watch out for, or would you think this works? Note: This patch uses entity migration, but we don't actually test that the migration works. I'm not sure it necessary considering how simple the code is. (And migration is tested at base.Entity level, I think!)
Attachment #8636806 -
Flags: review?(garndt)
Attachment #8636806 -
Flags: feedback?(jhford)
Updated•9 years ago
|
Attachment #8636806 -
Flags: review?(garndt) → review+
Comment 2•9 years ago
|
||
Comment on attachment 8636806 [details] [review] Github PR (In reply to Jonas Finnemann Jensen (:jonasfj) from comment #1) > Created attachment 8636806 [details] [review] > Github PR > > @jhford, you're the only one who has actually used base.Entity migration in > production. Is there anything I should watch out for, or would you think > this works? You mentioned to me that I should be returning a new object from the migration function instead of modifying the one that's passed in... I think you said that either works. In this case, the modification is so simple it's probably fine. > Note: > This patch uses entity migration, but we don't actually test that the > migration > works. I'm not sure it necessary considering how simple the code is. > (And migration is tested at base.Entity level, I think!) It looks like it should work given my experience with migration. I found the experience to be mostly nice, except for when I made a camelcasing typo and had to add a silly cleanup thing in the http api :)
Attachment #8636806 -
Flags: feedback?(jhford) → feedback+
Assignee | ||
Comment 3•9 years ago
|
||
Deployed to production and tasks can still be submitted... I hope the world isn't coming to an end...
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Blocks: q3-bb-tc-migration
Updated•5 years ago
|
Component: Queue → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•