|
||||||||
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 Disappear from Build History after Completion
nanzal...@achievementnetwork.org (JIRA) Wed, 19 Dec 2012 12:20:48 -0800
- [JIRA] (JENKINS-15156) Builds Disa... cameron.h...@boxtone.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... anton.hagl...@ericsson.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... fderu...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... johno.crawf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... tatiana.kalp...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... tatiana.kalp...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... anton.hagl...@ericsson.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... christian.koeb...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... nanzal...@achievementnetwork.org (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... tylerohl...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... nanzal...@achievementnetwork.org (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... tylerohl...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... wolfg1...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... wolfg1...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... s.sog...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... wolfg1...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... damian.di...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... larry.ca...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... nickolay.marti...@hp.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... martin.wiklu...@ericsson.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Disa... martin.wiklu...@ericsson.com (JIRA)
I just started using Jenkins about a month ago, and it was happening with some frequency on stand-alone server (no master/slave setup). I haven't seen the problem in the last 2 weeks however. As per D C's comment, reloading from disk resolves the issue whenever I see it.
edit: just happened again a few minutes ago. may have been caused by renaming. renamed the job in question to make way for a better implementation of the same job, but I've done the same thing to a few others without seeing this.