|
||||||||
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-14107) Unable to monitor e... chris.p.bai...@gmail.com (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... je...@artefactual.com (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... da...@gamehouse.com (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... aa...@rapleaf.com (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... da...@gamehouse.com (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... da...@gamehouse.com (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... da...@gamehouse.com (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... da...@gamehouse.com (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... aa...@rapleaf.com (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14107) Unable to moni... dogf...@java.net (JIRA)
Aaron, thanks that worked.
I downgraded to 1.464 and re-ran the ls -l example and it worked.
So newer versions have broken the ability to monitor external jobs.