Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
[FIXED JENKINS-15583]
Report 100 recent builds in the JSON API, including in-progress builds. Not reporting all the builds since this would nullify the lazy loading effect. Will introduce a pagenation API that supports retrieval.
- Loading branch information
Showing
3 changed files
with
12 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Even 100 seems like possibly too many; I was just looking at someone’s thread dump recently and it showed lots of activity servicing the recent build list, even though they were probably not even using this information. Ideally everyone would start using
tree
to pick out what they actually want, but in the meantime is it incompatible to lower thevisibility
of expensive things like this?