|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I think this is a more general issue, not related to just build info, that should be implemented.
I discussed this "allBuilds" endpoint with my colleague who is building front-end apps with the Jenkins API and, while it does work, they still maintained it would be useful to have paging with limit/offset parameters.
Mainly because loading all builds takes a long time, but also because semantically it doesn't make sense that you must switch from "builds" to "allBuilds" just to retrieve a larger result set.