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

Publish over SSH log the output of the exec global option

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • None
    • Jenkins 2.249.2
      Publish over SSH 1.21

    Description

      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.

      Attachments

        Issue Links

          Activity

            malice00 Roland Asmann created issue -
            porkrines42 Travis Abdelhamed made changes -
            Field Original Value New Value
            Attachment image-2020-11-17-15-56-46-618.png [ 53379 ]
            porkrines42 Travis Abdelhamed made changes -
            Attachment image-2020-11-17-15-56-57-559.png [ 53380 ]
            timja Tim Jacomb made changes -
            Issue Type Bug [ 1 ] Improvement [ 4 ]
            timja Tim Jacomb made changes -
            Summary Publish over SSH doesn't log the output of the exec anymore Publish over SSH log the output of the exec global option
            timja Tim Jacomb made changes -
            Description 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.
            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.
            bcoveny Bruce Coveny made changes -
            Link This issue is related to JENKINS-65170 [ JENKINS-65170 ]
            gmcdonald Gavin McDonald made changes -
            Resolution Incomplete [ 4 ]
            Status Open [ 1 ] Closed [ 6 ]

            People

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

              Dates

                Created:
                Updated:
                Resolved: