Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-47425

Do not print a stack trace on remoting connection error

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • remoting
    • None

    Description

      It is a possible condition and just pollutes the logs

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          csanchez Carlos Sanchez created issue -
          csanchez Carlos Sanchez made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]
          csanchez Carlos Sanchez made changes -
          Status In Progress [ 3 ] In Review [ 10005 ]
          csanchez Carlos Sanchez added a comment -

          PR https://github.com/jenkinsci/remoting/pull/202

          csanchez Carlos Sanchez added a comment - PR https://github.com/jenkinsci/remoting/pull/202
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Carlos Sanchez
          Path:
          src/main/java/org/jenkinsci/remoting/engine/JnlpAgentEndpointResolver.java
          http://jenkins-ci.org/commit/remoting/a450c9e4d9dbd235cdd91af04f53a500a3a55788
          Log:
          JENKINS-47425 Do not print a stack trace on connection error (#202)

          • Do not print a stack trace on connection error

          It is a possible condition and just pollutes the logs

          • JENKINS-47425 Do not print a stack trace on remoting connection error

          It is a possible condition and just pollutes the logs

          • retry again -> try again
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Carlos Sanchez Path: src/main/java/org/jenkinsci/remoting/engine/JnlpAgentEndpointResolver.java http://jenkins-ci.org/commit/remoting/a450c9e4d9dbd235cdd91af04f53a500a3a55788 Log: JENKINS-47425 Do not print a stack trace on connection error (#202) Do not print a stack trace on connection error It is a possible condition and just pollutes the logs JENKINS-47425 Do not print a stack trace on remoting connection error It is a possible condition and just pollutes the logs retry again -> try again
          csanchez Carlos Sanchez made changes -
          Resolution Fixed [ 1 ]
          Status In Review [ 10005 ] Resolved [ 5 ]
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Oleg Nenashev
          Path:
          pom.xml
          http://jenkins-ci.org/commit/jenkins/bcd0b2c72bf8c55b7d4997e142954c149b7d4faa
          Log:
          Update Remoting from 3.13. to 3.14

          Fixes JENKINS-45294, JENKINS-47425, JENKINS-47901, JENKINS-47942 + about 50 reported FindBugs issues (JENKINS-37566). There are 13 FindBugs issues left, work in progress.

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/jenkins/bcd0b2c72bf8c55b7d4997e142954c149b7d4faa Log: Update Remoting from 3.13. to 3.14 Fixes JENKINS-45294 , JENKINS-47425 , JENKINS-47901 , JENKINS-47942 + about 50 reported FindBugs issues ( JENKINS-37566 ). There are 13 FindBugs issues left, work in progress.
          oleg_nenashev Oleg Nenashev added a comment -

          The patch has been released in Remoting 3.14 and integrated towards Jenkins 2.90

          oleg_nenashev Oleg Nenashev added a comment - The patch has been released in Remoting 3.14 and integrated towards Jenkins 2.90
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Oleg Nenashev
          Path:
          pom.xml
          http://jenkins-ci.org/commit/jenkins/94250ec1caae0ed6d3096e7002e0c2fd42c557e1
          Log:
          Update Remoting from 3.13. to 3.14

          Fixes JENKINS-45294, JENKINS-47425, JENKINS-47901, JENKINS-47942 + about 50 reported FindBugs issues (JENKINS-37566). There are 13 FindBugs issues left, work in progress.

          (cherry picked from commit bcd0b2c72bf8c55b7d4997e142954c149b7d4faa)

          Compare: https://github.com/jenkinsci/jenkins/compare/c624f66dc408...94250ec1caae

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/jenkins/94250ec1caae0ed6d3096e7002e0c2fd42c557e1 Log: Update Remoting from 3.13. to 3.14 Fixes JENKINS-45294 , JENKINS-47425 , JENKINS-47901 , JENKINS-47942 + about 50 reported FindBugs issues ( JENKINS-37566 ). There are 13 FindBugs issues left, work in progress. (cherry picked from commit bcd0b2c72bf8c55b7d4997e142954c149b7d4faa) Compare: https://github.com/jenkinsci/jenkins/compare/c624f66dc408...94250ec1caae

          People

            csanchez Carlos Sanchez
            csanchez Carlos Sanchez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: