Closed
Bug 1188882
Opened 10 years ago
Closed 10 years ago
add support for task.priority to buildbot bridge
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
Details
Attachments
(2 files)
|
38 bytes,
text/x-github-pull-request
|
catlee
:
review+
|
Details | Review |
|
1.59 KB,
patch
|
catlee
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
From e-mail:
Additional note, when creating a task with task.priority: high,
the following scopes is required:
queue:task-priority:high
(Nothing is needed for "normal", which is default).
> I imagine we'll want to make use of this in the BuildBot Bridge and for
> any scheduled or release-related tasks.
bb-bridge picks up pending tasks from pulse and not through pollTaskUrls,
but yes it certainly could relay task.priority into the buildbot scheduling
database.
|
Assignee | |
Comment 1•10 years ago
|
||
|
||
Updated•10 years ago
|
Attachment #8641711 -
Flags: review?(catlee) → review+
|
|
Assignee | |
Comment 2•10 years ago
|
||
Restarting should be fine. Anything that gets interrupt will get requeued...
Attachment #8643078 -
Flags: review?(catlee)
|
|
||
Updated•10 years ago
|
Attachment #8643078 -
Flags: review?(catlee) → review+
|
|
Assignee | |
Updated•10 years ago
|
Attachment #8643078 -
Flags: checked-in+
|
|
Assignee | |
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
|
||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•