|
||||||||
|
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-15156) Builds Disa... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)
- [JIRA] (JENKINS-15156) Builds... [email protected] (JIRA)

I have the same problem (1.485). Builds disappear from the history. Often only the most recent build is visible.
Attempting to access the URL of the missing builds manually (ie. append /51 to the job URL) produces a 404 Status Error (sorry, don't have exact text).
Confirmed that "Reload configuration from disk" fixes the problem - full build history is again visible, and the build URLs can be accessed manually too.