[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents

[jgl...@cloudbees.com (JIRA)]

Title: Message Title

Jesse Glick commented on JENKINS-55257   Re: Timestamper break builds on Windows agents I’m not very familiar with jar files but they’re just zip files, right? Correct. Short of a known way to reproduce this error from scratch in a fresh installation of Jenkins, the diagnostic path I would start with is opening the Groovy console on an affected agent and running [hudson.remoting.Channel, org.jenkinsci.remoting.util.AnonymousClassWarnings]*.protectionDomain.codeSource.location You would expect to see something like Result: [https://jenkins/jnlpJars/remoting.jar, https://host:jenkins/jnlpJars/remoting.jar] If you see something else, then we have a lead. If you see the above, then some other diagnostics would be needed. Configuration worked before and did not change, so it's definitely related to the update “Related” to the update perhaps, but that does not imply a bug in any software which was updated. Incidental changes in behavior often cause existing misconfigurations to become manifest. Similarly, my proposed rewrite in JENKINS-48344 would delete the code path which evidently triggers this problem, but that does not make it a “fix” for this issue. Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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/d/optout.