|
||||||||
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-15799) loosing matrix sub builds
ann.campb...@shawinc.com (JIRA) Mon, 03 Dec 2012 04:50:48 -0800
- [JIRA] (JENKINS-15799) loosing matrix ... thomas.reini...@micronova.de (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... zka...@nds.com (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... thomas.reini...@micronova.de (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... aba...@java.net (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... aba...@java.net (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... ann.campb...@shawinc.com (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... gjschip...@solcon.nl (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... gjschip...@solcon.nl (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... gjschip...@solcon.nl (JIRA)
The ticket I opened got closed as a duplicate of this one. I saw this "forgetting" behavior with a renamed, top-level, non-matrix job. Right after renaming the job, the builds showed in the history, but ... several hours later they were gone (altho still there on disk.)