Correcting API documentation of builds vs. allBuilds (#10112)

jenkinsci · Jan 3, 2025 · d3e8908 · d3e8908
1 parent 89f48c5
commit d3e8908
Showing 1 changed file with 1 addition and 1 deletion.
diff --git 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.
   <h2>Retrieving all builds</h2>
   <p>
     To prevent Jenkins from having to load all builds from disk when someone accesses the job API, the <code>builds</code>
-    tree only contains the 50 newest builds. If you really need to get all builds, access the <code>allBuilds</code> tree,
+    tree only contains the 100 newest builds. If you really need to get all builds, access the <code>allBuilds</code> tree,
     e.g. by fetching <code>…/api/xml?tree=allBuilds[…]</code>. Note that this may result in significant performance degradation
     if you have a lot of builds in this job.
   </p>