Key: |
QB-675
|
Type: |
Improvement
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Unassigned
|
Reporter: |
Roger Perkins
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 12/Oct/10 04:27 PM
Updated: 14/Oct/10 11:13 AM
|
|
|
Component/s: |
None
|
Affects Version/s: |
3.0.11
|
Fix Version/s: |
3.0.12
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
The build queue in 3.x now adds new builds to the start. I have a lot of configurations that are checked every 5 minutes for changes, these now go onto the front of the queue and very rapidly push the currently building jobs off onto the fourth page. Surely the new queue items should go on the end as they did in QB 2.x?
The build queue is also full now of what is very confusing items for my users. It seems the condition check for a configuration is now deffered until it makes it to the front of the queue, resulting in the queue filling up with dozens and dozens of entries that will ultimately do nothing and make it very hard to see what is actually scheduled to run in the queue.
|
Description
|
The build queue in 3.x now adds new builds to the start. I have a lot of configurations that are checked every 5 minutes for changes, these now go onto the front of the queue and very rapidly push the currently building jobs off onto the fourth page. Surely the new queue items should go on the end as they did in QB 2.x?
The build queue is also full now of what is very confusing items for my users. It seems the condition check for a configuration is now deffered until it makes it to the front of the queue, resulting in the queue filling up with dozens and dozens of entries that will ultimately do nothing and make it very hard to see what is actually scheduled to run in the queue. |
Show » |
|