|
||||||||
|
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 ... [email protected] (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... [email protected] (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... [email protected] (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... [email protected] (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... [email protected] (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... [email protected] (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... [email protected] (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... [email protected] (JIRA)
- [JIRA] (JENKINS-15799) loosing ma... [email protected] (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.)