From 3a83fe3c0b295909d6a314777aee2c6728860e3a Mon Sep 17 00:00:00 2001 From: Jesse Glick Date: Thu, 2 Jan 2025 15:28:08 -0500 Subject: [PATCH] Correcting API documentation of `builds` vs. `allBuilds` --- core/src/main/resources/hudson/model/Job/_api.jelly | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/src/main/resources/hudson/model/Job/_api.jelly b/core/src/main/resources/hudson/model/Job/_api.jelly index 28a161afbb65..652a44c4ec56 100644 --- a/core/src/main/resources/hudson/model/Job/_api.jelly +++ b/core/src/main/resources/hudson/model/Job/_api.jelly @@ -30,7 +30,7 @@ THE SOFTWARE.

Retrieving all builds

To prevent Jenkins from having to load all builds from disk when someone accesses the job API, the builds - tree only contains the 50 newest builds. If you really need to get all builds, access the allBuilds tree, + tree only contains the 100 newest builds. If you really need to get all builds, access the allBuilds tree, e.g. by fetching …/api/xml?tree=allBuilds[…]. Note that this may result in significant performance degradation if you have a lot of builds in this job.