Skip to content

[JENKINS-47425] Do not print a stack trace on remoting connection error #1279

Closed

Description

@jenkins-infra-bot

It is a possible condition and just pollutes the logs


Originally reported by csanchez, imported from: Do not print a stack trace on remoting connection error
  • assignee: csanchez
  • status: Resolved
  • priority: Minor
  • component(s): remoting
  • resolution: Fixed
  • resolved: 2017-10-16T08:52:58+00:00
  • votes: 0
  • watchers: 3
  • imported: 2025-11-25
Raw content of original issue

It is a possible condition and just pollutes the logs

Activity

  1. jenkins-infra-bot commented on Oct 13, 2017

    @jenkins-infra-bot
    Author
    csanchez:

    PR #202

  2. jenkins-infra-bot commented on Oct 16, 2017

    @jenkins-infra-bot
    Author
    scm_issue_link:
    • Original comment link
    • Raw content of original 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

    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
  3. jenkins-infra-bot commented on Nov 12, 2017

    @jenkins-infra-bot
    Author
    scm_issue_link:

    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.

  4. jenkins-infra-bot commented on Nov 13, 2017

    @jenkins-infra-bot
    Author
    oleg_nenashev:
    • Original comment link
    • Raw content of original comment:

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

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

  5. jenkins-infra-bot commented on Nov 22, 2017

    @jenkins-infra-bot
    Author
    scm_issue_link:

    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: jenkinsci/jenkins@c624f66...94250ec

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions