| Key: |
CIB-1970
|
| Type: |
New Feature
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
4
|
| Assignee: |
jason
|
| Reporter: |
Rohan McGovern
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 12/May/09 10:29 PM
Updated: 16/Jun/09 12:53 AM
|
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
2.1.4,
2.0.32
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
It would be nice if the remote API provided a way to get information on queued builds and to cancel queued builds. There are functions to manipulate builds but it doesn't seem possible to use them with queued builds, since queued builds don't yet have a build ID.
Use case: we had a rule which queued 184 builds overnight, at which point we stopped using "scm trigger" for that project since we clearly couldn't keep up. But AFAICT getting rid of the 184 builds requires 184 clicks in the web UI. Typically I use the remote API for things like that to avoid fatigue of index finger.
|
|
Description
|
It would be nice if the remote API provided a way to get information on queued builds and to cancel queued builds. There are functions to manipulate builds but it doesn't seem possible to use them with queued builds, since queued builds don't yet have a build ID.
Use case: we had a rule which queued 184 builds overnight, at which point we stopped using "scm trigger" for that project since we clearly couldn't keep up. But AFAICT getting rid of the 184 builds requires 184 clicks in the web UI. Typically I use the remote API for things like that to avoid fatigue of index finger. |
Show » |
|
Include build queue management in remote API
Thanks for the suggestion.
Re: the builds piling up in the queue, did you have changelist isolation turned on? If you can't keep up with builds, switching this build option off should ensure that Pulse will not continue to pile up requests for the same project. Instead it keeps the revision of the queued build floating and fixes it to the latest revision when the build commences. So if more new revisions appear while a build is queued, they do not add to the queue.