|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I was trying to create some script to crosscheck locally available builds with the ones reported on web page using REST api appending to job "/api/json?tree=builds[number]" and noticed something curious, not all builds are reported in that list when comparing with the ones actually visible in build history, only the most recent ones on variable ammount.
Not sure if there is any limitation/restriction to the api, but maybe this is a symptom of this problem because if it already thinks it has less builds that it actually has, on some cleanup procedure it might only keep the ones reported and discard the rest.