Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-15704

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

      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.

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

          Overmind DL1 added a comment -

          Also experiencing this issue with Jenkins ver. 1.489.

          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.

          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.

          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.

          Eduardo Gonzalez added a comment - 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.

          pedro reis added a comment -

          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)

          pedro reis added a comment - 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)

          pedro reis added a comment -

          also occurs in python api

          pedro reis added a comment - also occurs in python api

          Is there a suggested work around atleast?

          Dhawal Bhanushali added a comment - Is there a suggested work around atleast?

          pedro reis added a comment -

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

          pedro reis added a comment - Yes, I'm now using "lastBuild" element instead of "builds" element.

          Jesse Glick added a comment -

          I think just a duplicate of JENKINS-15583.

          Jesse Glick added a comment - I think just a duplicate of JENKINS-15583 .

            ndeloof Nicolas De Loof
            dank Daniel Kaplan
            Votes:
            7 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: