[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Dan Lewis commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows We are running 1.514 and have this issue. It causes tons of stack traces which slows performance. I have filtered out the messages in the logging config which helps. +1 getting it into 1.509.2 because we want to move to LTS but won't until this is fixed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS
Dan Lewis edited a comment on JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS This might be related to issue JENKINS-17681 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS
Dan Lewis commented on JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS This might be related to issue https://issues.jenkins-ci.org/browse/JENKINS-17681 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS
Dan Lewis commented on JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS This continues to occur in 1.512. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [logging] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042
Dan Lewis commented on JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042 am I using logging plugin? no. but I didn't know what module to put in for this problem? Help? It's not clear to me from the stack trace where this problem is coming from. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [logging] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042
Dan Lewis commented on JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042 setup? dedicated master with 9 slaves, all windows 7 building Java programs using freestyle ant using svn i get these warnings for all of my jobs, starting with build 1.510 (we skipped from 1.506 to 1.510). i have even resaved all of my jobs using 1.510 to no avail. i changed my logging to exclude everything from jenkins.model.PeepholePermalink below severe 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162542#comment-162542 ] Dan Lewis commented on JENKINS-11381: - agree. bonus points if we can fail fast with an appropriate error message explaining corrective procedure, e.g. jenkins does not support auto-update of pre-SVN 1.7 workspaces to 1.7; please remove workspaces and restart build or some such Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
