|
||||||||
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-13614) archiving artefa... chrisgw...@gmail.com (JIRA)
- [JIRA] (JENKINS-13614) archiving a... nickolay.marti...@hp.com (JIRA)
- [JIRA] (JENKINS-13614) archiving a... chrisgw...@gmail.com (JIRA)
- [JIRA] (JENKINS-13614) archiving a... chrisgw...@gmail.com (JIRA)
- [JIRA] (JENKINS-13614) archiving a... brett.dellegra...@gmail.com (JIRA)
- [JIRA] (JENKINS-13614) archiving a... nickolay.marti...@hp.com (JIRA)
- [JIRA] (JENKINS-13614) archiving a... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-13614) archiving a... nickolay.marti...@hp.com (JIRA)
- [JIRA] (JENKINS-13614) archiving a... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-13614) archiving a... brett.dellegra...@gmail.com (JIRA)
- [JIRA] (JENKINS-13614) archiving a... hinr...@prostep.com (JIRA)
- [JIRA] (JENKINS-13614) archiving a... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-13614) archiving a... smyau...@gmail.com (JIRA)
- [JIRA] (JENKINS-13614) archiving a... nickolay.marti...@hp.com (JIRA)
1.482 appears to resolve the readlink issue for me. The builds that succeed, but were being failed by Jenkins, no longer do so. Can others confirm?