[JIRA] (JENKINS-15704) Incomplete list of builds when I go to JobName/api/json

Daniel Kaplan created JENKINS-15704

Incomplete list of builds when I go to JobName/api/json

Issue Type:	Bug
Affects Versions:	current
Assignee:	Nicolas De Loof
Attachments:	json.txt, screenshot.png
Components:	build-flow, promoted-builds
Created:	02/Nov/12 5:21 PM
Description:	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.
Project:	Jenkins
Priority:	Major
Reporter:	Daniel Kaplan

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

Kohsuke Kawaguchi updated JENKINS-15704

Incomplete list of builds when I go to JobName/api/json

Change By:	Kohsuke Kawaguchi (02/Nov/12 7:09 PM)
Attachment:	json.txt

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

Daniel Kaplan updated JENKINS-15704

Incomplete list of builds when I go to JobName/api/json

Change By:

Daniel Kaplan (02/Nov/12 7:18 PM)

Description:

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 In  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.

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

Jerry Maloney commented on JENKINS-15704

Incomplete list of builds when I go to JobName/api/json

I have this issue as well. The json object returned only ever includes ten builds, even though there are really many more than that.

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

Overmind DL1 commented on JENKINS-15704

Incomplete list of builds when I go to JobName/api/json

Also experiencing this issue with Jenkins ver. 1.489.

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

Mitch Dempsey commented on JENKINS-15704

Incomplete list of builds when I go to JobName/api/json

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.

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

Overmind DL1 commented on JENKINS-15704

Incomplete list of builds when I go to JobName/api/json

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.

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

 

Overmind DL1 edited a comment on JENKINS-15704

Incomplete list of builds when I go to JobName/api/json

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.

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

Michaael G commented on JENKINS-15704

Incomplete list of builds when I go to JobName/api/json

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.

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

Eduardo Gonzalez commented on JENKINS-15704

Incomplete list of builds when I go to JobName/api/json

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.

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

pedro reis commented on JENKINS-15704

Incomplete list of builds when I go to JobName/api/json

This happens also in Python Remote API. This started to happen when upgraded to Jenkins 1.491. The "lastBuild" element is immediately updated but the "builds" element is not! (And this caused problems in our building and dependencies system)

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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Dhawal Bhanushali commented on JENKINS-15704

Incomplete list of builds when I go to JobName/api/json

Is there a suggested work around atleast?

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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

pedro reis commented on JENKINS-15704

Incomplete list of builds when I go to JobName/api/json

Yes, I'm now using "lastBuild" element instead of "builds" element.

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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Jesse Glick resolved JENKINS-15704 as Duplicate

Incomplete list of builds when I go to JobName/api/json

I think just a duplicate of JENKINS-15583.
Change By:	Jesse Glick (13/Mar/13 10:41 PM)
Status:	Open Resolved
Resolution:	Duplicate

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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.