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

Publish over SSH log the output of the exec global option

    • Icon: Improvement Improvement
    • Resolution: Incomplete
    • Icon: Major Major
    • None
    • Jenkins 2.249.2
      Publish over SSH 1.21

      See https://issues.jenkins.io/browse/JENKINS-64101?focusedCommentId=401329&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-401329 for how to re-enable logging

      We updated to the latest version of the plugin last week and noticed that our jobs don't write the output of the commands that are executed on the remote server anymore.

      For most Jobs this is not a big issue, but we have some that actually parse the Jenkins log for this output, which now actually fail (although the SSH works).

       The actual output in the 'before' screenshot is obviously cut because of sensitive information.

          [JENKINS-64101] Publish over SSH log the output of the exec global option

          Roland Asmann created issue -
          Travis Abdelhamed made changes -
          Attachment New: image-2020-11-17-15-56-46-618.png [ 53379 ]
          Travis Abdelhamed made changes -
          Attachment New: image-2020-11-17-15-56-57-559.png [ 53380 ]
          Tim Jacomb made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          Tim Jacomb made changes -
          Summary Original: Publish over SSH doesn't log the output of the exec anymore New: Publish over SSH log the output of the exec global option
          Tim Jacomb made changes -
          Description Original: We updated to the latest version of the plugin last week and noticed that our jobs don't write the output of the commands that are executed on the remote server anymore.

          For most Jobs this is not a big issue, but we have some that actually parse the Jenkins log for this output, which now actually fail (although the SSH works).

           The actual output in the 'before' screenshot is obviously cut because of sensitive information.
          New: h2. See https://issues.jenkins.io/browse/JENKINS-64101?focusedCommentId=401329&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-401329 for how to re-enable logging

          We updated to the latest version of the plugin last week and noticed that our jobs don't write the output of the commands that are executed on the remote server anymore.

          For most Jobs this is not a big issue, but we have some that actually parse the Jenkins log for this output, which now actually fail (although the SSH works).

           The actual output in the 'before' screenshot is obviously cut because of sensitive information.
          Bruce Coveny made changes -
          Link New: This issue is related to JENKINS-65170 [ JENKINS-65170 ]
          Gavin McDonald made changes -
          Resolution New: Incomplete [ 4 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            malice00 Roland Asmann
            Votes:
            3 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: