[JIRA] [core] (JENKINS-22977) Add results paging to the Jenkins API

[dan...@beckweb.net (JIRA)]

Daniel Beck commented on JENKINS-22977 Add results paging to the Jenkins API semantically it doesn't make sense that you must switch from "builds" to "allBuilds" just to retrieve a larger result set. Returning all builds used to be essentially free. As of 1.485, it's insanely expensive. What would be a better solution, breaking backwards compatibility? There's a lot of things weird in Jenkins, but caused by the desire to remain backward compatible. Pagination API already exists, it's called XPath. https://builds.apache.org/job/PDFBox-ant/api/xml?tree=allBuilds[number]&xpath=//allBuild[position%28%29%3C=10]&wrapper=builds https://builds.apache.org/job/PDFBox-ant/api/xml?tree=allBuilds[number]&xpath=//allBuild[position%28%29%3E10%20and%20position%28%29%3C=20]&wrapper=builds

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.