|
||||||||
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 Disappea... jchat...@acuitus.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Dis... pet...@standingwave.org (JIRA)
- [JIRA] (JENKINS-15156) Builds Dis... ivaylo.brat...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Dis... jo...@joelj.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Dis... andrzej.pasterc...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Dis... nickolay.marti...@hp.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Dis... nickolay.marti...@hp.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Dis... martin.danjo...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Dis... nickolay.marti...@hp.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Dis... henri.go...@gmail.com (JIRA)
- [JIRA] (JENKINS-15156) Builds Dis... henri.go...@gmail.com (JIRA)
For reference, we're seeing this issue under 1.486, on a Maven job running exclusively on the master. Other apparently identically set up Maven jobs (also running on the master) don't exhibit the same problem, however.
As a possibly-related issue, the jobs where builds disappear have also shown just build status vanishing as well - several early builds had test failures, and every now and then those builds turn up as blue (before eventually vanishing entirely); in both cases, reloading configuration from disk temporarily resolves the issue.