-
Bug
-
Resolution: Duplicate
-
Major
-
None
I see a different list of builds when I go to JobName/api/json as I do when I go to JobName from the UI. JobName/api/json has a few less builds and it's even excluding promoted builds at the bottom which is a blocker for our company.
In the JSON build number 253 is nowhere to be found even though it's a promoted build and listed on the UI.
- duplicates
-
-
- Resolved
-
- is related to
-
-
- Resolved
-
[JENKINS-15704] Incomplete list of builds when I go to JobName/api/json
Daniel Kaplan
created issue -
| Attachment | Original: json.txt [ 22772 ] |
Daniel Kaplan
made changes -
| Description |
Original:
I see a different list of builds when I go to JobName/api/json as I do when I go to JobName from the UI. JobName/api/json has a few less builds and it's even excluding promoted builds at the bottom which is a blocker for our company. I've attached the JSON that we see and a screenshot of the builds on the UI. You can see in the JSON that build number 253 is nowhere to be found even though it's a promoted build and listed on the UI. |
New:
I see a different list of builds when I go to JobName/api/json as I do when I go to JobName from the UI. JobName/api/json has a few less builds and it's even excluding promoted builds at the bottom which is a blocker for our company. In the JSON build number 253 is nowhere to be found even though it's a promoted build and listed on the UI. |
Guy Rozendorn
made changes -
| Link |
New:
This issue is related to |
Overmind DL1
added a comment - Also experiencing this issue with Jenkins ver. 1.489. 
Mitch Dempsey
added a comment - This is caused by 'hudson.util.RunList' in the function named 'newBuilds()'
The .limit call is hard coded to show the last 10 builds. This should probably be a configuration option, or should just show all.
Mitch Dempsey
added a comment - This is caused by 'hudson.util.RunList' in the function named 'newBuilds()'
The .limit call is hard coded to show the last 10 builds. This should probably be a configuration option, or should just show all. For note, it is not showing the 'last' 10, it is showing 10 after the last 1. Currently we build the changelog from it (so we want it to show all, not 10), and it is not showing the current one either. Whenever we get the list from jenkins it omits the current one, gets the ten before it, and omits the remainder. We need all.
Back when we ran the version about 5 builds ago (??7) it did show all including the current. It worked properly at that point, hence why this is a regression.
Overmind DL1
added a comment - - edited For note, it is not showing the 'last' 10, it is showing 10 after the last 1. Currently we build the changelog from it (so we want it to show all , not 10), and it is not showing the current one either. Whenever we get the list from jenkins it omits the current one, gets the ten before it, and omits the remainder. We need all .
Back when we ran the version about 5 builds ago (??7) it did show all including the current. It worked properly at that point, hence why this is a regression. 
Michaael G
added a comment - As a user of a jenkins project, this is bothering me also. The issue I have is what Overmind reports – the changelog doesn't tell me the most recent change, so other than using the "recommended" version (the project in question is basically a modding API, and it is updated as new mods for a base program need new features, with various mods wanting different versions), I'm generally trying to find the most recent one that seems stable, that hasn't broken compatibility for a new feature, that hasn't started on a new project/task, and I can't tell what the most recent version is doing.
Michaael G
added a comment - As a user of a jenkins project, this is bothering me also. The issue I have is what Overmind reports – the changelog doesn't tell me the most recent change, so other than using the "recommended" version (the project in question is basically a modding API, and it is updated as new mods for a base program need new features, with various mods wanting different versions), I'm generally trying to find the most recent one that seems stable, that hasn't broken compatibility for a new feature, that hasn't started on a new project/task, and I can't tell what the most recent version is doing. I also have the same problem, in api/xml. I upgraded from 1.479 to 1.499 to find this issue. It bothers me a lot since I use the API from another web pages to obtain data. Now it's no good. I am seriously thinking in downgrade jenkins.
I have this issue as well. The json object returned only ever includes ten builds, even though there are really many more than that.