[JIRA] [remoting] (JENKINS-35494) Remoting Launcher does not handle exceptional cases
Title: Message Title Oleg Nenashev commented on JENKINS-35494 Re: Remoting Launcher does not handle exceptional cases Releases: remoting-2.60 and jenkins-2.9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [remoting] (JENKINS-35494) Remoting Launcher does not handle exceptional cases
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-35494 Remoting Launcher does not handle exceptional cases Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [remoting] (JENKINS-35494) Remoting Launcher does not handle exceptional cases
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35494 Re: Remoting Launcher does not handle exceptional cases Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/jenkins/c718516adfddeb10cbf616ce37c619cc6bbafd53 Log: Update remoting to 2.60 (#2403) Changes summary: Fixed issues: JENKINS-22722(https://issues.jenkins-ci.org/browse/JENKINS-22722) - Make the channel reader tolerant against Socket timeouts. (https://github.com/jenkinsci/remoting/pull/80) JENKINS-32326 (https://issues.jenkins-ci.org/browse/JENKINS-32326) - Support no_proxy environment variable. (https://github.com/jenkinsci/remoting/pull/84) JENKINS-35190(https://issues.jenkins-ci.org/browse/JENKINS-35190) - Do not invoke PingFailureAnalyzer for agent=>master ping failures. (https://github.com/jenkinsci/remoting/pull/85) JENKINS-31256(https://issues.jenkins-ci.org/browse/JENKINS-31256) - hudson.Remoting.Engine#waitForServerToBack now uses credentials for connection. (https://github.com/jenkinsci/remoting/pull/87) JENKINS-35494(https://issues.jenkins-ci.org/browse/JENKINS-35494) - Fix issues in file management in hudson.remoting.Launcher (main executable class). (https://github.com/jenkinsci/remoting/pull/88) Enhancements: Ensure a message is logged if remoting fails to override the default ClassFilter. (https://github.com/jenkinsci/remoting/pull/80) Add Comment
[JIRA] [remoting] (JENKINS-35494) Remoting Launcher does not handle exceptional cases
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35494 Re: Remoting Launcher does not handle exceptional cases Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/jenkins/d9f12b0e614d9598221c571001aa43c018b21e25 Log: Update remoting to 2.60 Changes summary: Fixed issues: JENKINS-22722(https://issues.jenkins-ci.org/browse/JENKINS-22722) - Make the channel reader tolerant against Socket timeouts. (https://github.com/jenkinsci/remoting/pull/80) JENKINS-32326 (https://issues.jenkins-ci.org/browse/JENKINS-32326) - Support no_proxy environment variable. (https://github.com/jenkinsci/remoting/pull/84) JENKINS-35190(https://issues.jenkins-ci.org/browse/JENKINS-35190) - Do not invoke PingFailureAnalyzer for agent=>master ping failures. (https://github.com/jenkinsci/remoting/pull/85) JENKINS-31256(https://issues.jenkins-ci.org/browse/JENKINS-31256) - hudson.Remoting.Engine#waitForServerToBack now uses credentials for connection. (https://github.com/jenkinsci/remoting/pull/87) JENKINS-35494(https://issues.jenkins-ci.org/browse/JENKINS-35494) - Fix issues in file management in hudson.remoting.Launcher (main executable class). (https://github.com/jenkinsci/remoting/pull/88) Enhancements: Ensure a message is logged if remoting fails to override the default ClassFilter. (https://github.com/jenkinsci/remoting/pull/80) Add Comment
[JIRA] [remoting] (JENKINS-35494) Remoting Launcher does not handle exceptional cases
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35494 Re: Remoting Launcher does not handle exceptional cases Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/remoting/Launcher.java http://jenkins-ci.org/commit/remoting/4610a909f58ef9b3d33165d2c74963869f3936aa Log: JENKINS-35494 - FindBugs - fix minor File Management issues in hudson.remoting.Launcher (#88) [x] Tcp port temporary file is not being closed properly when running in the runAsTcpServer() mode [x] tcpPortFile deletion issues are not being logged [x] Resource input stream is not being closed correctly Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [remoting] (JENKINS-35494) Remoting Launcher does not handle exceptional cases
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-35494 Remoting Launcher does not handle exceptional cases Issue Type: Bug Assignee: Unassigned Components: remoting Created: 2016/Jun/09 11:31 AM Priority: Minor Reporter: Oleg Nenashev hudson.remoting.Launcher has several minor issues, which have been reported by FindBugs Tcp port temporary file is not being closed properly when running in the runAsTcpServer() mode tcpPortFile deletion issues are not being logged Resource input stream is not being closed correctly Add
[JIRA] [remoting] (JENKINS-35494) Remoting Launcher does not handle exceptional cases
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-35494 Remoting Launcher does not handle exceptional cases Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [remoting] (JENKINS-35494) Remoting Launcher does not handle exceptional cases
Title: Message Title Oleg Nenashev started work on JENKINS-35494 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
