If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 09/Sep/14 07:44 PM
Updated: 11/Sep/14 12:53 AM
|
|
|
Component/s: |
None
|
Affects Version/s: |
5.1.33
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Current REST API for query for build notifications is missing ability to query _incrementally_.
"last_notified_build_id" option is not sufficient, as when you query with e.g "last_notified_build_id=1", you get a list of builds with ids with gaps e.g. 1, 2, 5, and you don't know if builds 3 and 4 haven't yet completed, or you just have access rights to them, and you will never get notification on them.
So you don't know if next time you can query with last_notified_build_id=5 (because you will never get notifications about 3 and 4 due to permissions) or you should re-query with last_notified_build_id=1 (because the build are still running)
Instead there should last_status_date parameter, so that you could query for all notifications on builds that completed (either successfully or failed depending on your notification settings) after a specified date.
|
Description
|
Current REST API for query for build notifications is missing ability to query _incrementally_.
"last_notified_build_id" option is not sufficient, as when you query with e.g "last_notified_build_id=1", you get a list of builds with ids with gaps e.g. 1, 2, 5, and you don't know if builds 3 and 4 haven't yet completed, or you just have access rights to them, and you will never get notification on them.
So you don't know if next time you can query with last_notified_build_id=5 (because you will never get notifications about 3 and 4 due to permissions) or you should re-query with last_notified_build_id=1 (because the build are still running)
Instead there should last_status_date parameter, so that you could query for all notifications on builds that completed (either successfully or failed depending on your notification settings) after a specified date.
|
Show » |
No work has yet been logged on this issue.
|
|