|
||||||||
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 |
[JIRA] (JENKINS-15704) Incomplete list of builds when I go to JobName/api/json
overmind...@gmail.com (JIRA) Fri, 30 Nov 2012 11:44:47 -0800
- [JIRA] (JENKINS-15704) Incomplete list of ... d...@mirthcorp.com (JIRA)
- [JIRA] (JENKINS-15704) Incomplete lis... k...@kohsuke.org (JIRA)
- [JIRA] (JENKINS-15704) Incomplete lis... d...@mirthcorp.com (JIRA)
- [JIRA] (JENKINS-15704) Incomplete lis... gpjerrymalo...@gmail.com (JIRA)
- [JIRA] (JENKINS-15704) Incomplete lis... overmind...@gmail.com (JIRA)
- [JIRA] (JENKINS-15704) Incomplete lis... mit...@mirthcorp.com (JIRA)
- [JIRA] (JENKINS-15704) Incomplete lis... overmind...@gmail.com (JIRA)
- [JIRA] (JENKINS-15704) Incomplete lis... overmind...@gmail.com (JIRA)
- [JIRA] (JENKINS-15704) Incomplete lis... keybou...@gmail.com (JIRA)
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.