|
||||||||
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-15587) Builds disappear from j... ch...@orr.me.uk (JIRA)
- [JIRA] (JENKINS-15587) Builds disappear f... ch...@orr.me.uk (JIRA)
- [JIRA] (JENKINS-15587) Builds disappear f... alek...@java.net (JIRA)
- [JIRA] (JENKINS-15587) Builds disappear f... alek...@java.net (JIRA)
- [JIRA] (JENKINS-15587) Builds disappear f... alek...@java.net (JIRA)
- [JIRA] (JENKINS-15587) Builds disappear f... ant.ka...@gmail.com (JIRA)
- [JIRA] (JENKINS-15587) Builds disappear f... jos...@java.net (JIRA)
- [JIRA] (JENKINS-15587) Builds disappear f... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15587) Builds disappear f... rayd...@aol.com (JIRA)
- [JIRA] (JENKINS-15587) Builds disappear f... jos...@java.net (JIRA)
I believe I saw this too in the logs while debugging an issue a few weeks ago.
But it doesn't actually cause any problems, does it? All the builds are still visible in Jenkins, right?
Edit: Apparently I failed at fully reading the original post. But I'm sure I saw this on OS X, but didn't see any problems. Just that Jenkins was parsing the symlinked target directory names (i.e. the build number) as a date, then failing; the symlinks themselves (i.e. the datetime) seemed to be parsed and the builds appeared as normal.