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

Publish over SSH log the output of the exec global option

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Incomplete
    • Icon: Major Major
    • publish-over-ssh-plugin
    • 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.

        1. before.png
          before.png
          10 kB
        2. after.png
          after.png
          4 kB
        3. image-2020-11-17-15-56-46-618.png
          image-2020-11-17-15-56-46-618.png
          61 kB
        4. image-2020-11-17-15-56-57-559.png
          image-2020-11-17-15-56-57-559.png
          52 kB

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

          Roland Asmann created issue -

          Carlos Ruiz added a comment -

          Same here:

          Before:
          https://jenkins.idempiere.org/job/Restart%20test.idempiere.org/364/console

          After:
          https://jenkins.idempiere.org/job/Restart%20test.idempiere.org/377/console

           

          Carlos Ruiz added a comment - Same here: Before: https://jenkins.idempiere.org/job/Restart%20test.idempiere.org/364/console After: https://jenkins.idempiere.org/job/Restart%20test.idempiere.org/377/console  

          Roland Asmann added a comment -

          I just found out this was done in JENKINS-33455, which as the last comment says:

          I am not sure this is the best way to go, so I am soliciting feedback.

          Why is this in the release and why is there absolutely no mention of it in the release notes??

          Roland Asmann added a comment - I just found out this was done in JENKINS-33455 , which as the last comment says: I am not sure this is the best way to go, so I am soliciting feedback. Why is this in the release and why is there absolutely no mention of it in the release notes??

          Carlos Ruiz added a comment -

          Thanks malice00.

          So, it was just a new configurable option.

          I saw the Verbose output in console in the Advanced options, but I didn't dare to click on it because the help says:

          Select to enable an obscene amount of information to the Jenkins console - only really useful to help track down problems.

          I thought it was going to collapse my hard disk.

          I just tried, enabled that option and the command output is visible again.  So, maybe this is just a matter of lack of documentation.

           

           

           

          Carlos Ruiz added a comment - Thanks malice00 . So, it was just a new configurable option. I saw the Verbose output in console in the Advanced options, but I didn't dare to click on it because the help says: Select to enable an obscene amount of information to the Jenkins console - only really useful to help track down problems. I thought it was going to collapse my hard disk. I just tried, enabled that option and the command output is visible again.  So, maybe this is just a matter of lack of documentation.      

          aaron wong added a comment - - edited

          carlosruiz_globalqss you can down grade this plugin to old version, use offline mode to invoke this problem, and the plugin address :http://mirrors.jenkins-ci.org/plugins/publish-over-ssh/1.20/

          1.20 version is OK

          aaron wong added a comment - - edited carlosruiz_globalqss you can down grade this plugin to old version, use offline mode to invoke this problem, and the plugin address : http://mirrors.jenkins-ci.org/plugins/publish-over-ssh/1.20/ 1.20 version is OK

          Carlos Ruiz added a comment -

          Thanks awinlei, I think there is no need to downgrade, just check the Verbose output in console in the Advanced configuration of the shell task.

          Carlos Ruiz added a comment - Thanks awinlei , I think there is no need to downgrade, just check the Verbose output in console in the Advanced configuration of the shell task.

          Markus Kusserow added a comment - - edited

          Thanks malice00. This type of change should be communicated very clearly!

          We have a lot of jobs maintained by different employees. Until it is clear how this change should be dealt with, we will decide to downgrade and stay with version 1.20.1.

          It would be helpful if the default behavior could be configured system-wide and on a job basis the deviant behavior.

          Markus Kusserow added a comment - - edited Thanks malice00 . This type of change should be communicated very clearly! We have a lot of jobs maintained by different employees. Until it is clear how this change should be dealt with, we will decide to downgrade and stay with version 1.20.1. It would be helpful if the default behavior could be configured system-wide and on a job basis the deviant behavior.

          John Beckerle added a comment -

          I second the comment by Markus Kusserow. 

          We need the option to be able to configure the default behavior of the "Verbose output in console" option on a system wide basis.

          In our system we currently depend upon this output in multiple hundreds of projects.  Visiting each project just to change this setting is not a good use of time.  And I would rather not have to figure out how to do it with a global edit either.

          We have downgraded to version 1.20.1 for now.

          John Beckerle added a comment - I second the comment by Markus Kusserow.  We need the option to be able to configure the default behavior of the "Verbose output in console" option on a system wide basis. In our system we currently depend upon this output in multiple hundreds of projects.  Visiting each project just to change this setting is not a good use of time.  And I would rather not have to figure out how to do it with a global edit either. We have downgraded to version 1.20.1 for now.

          Sorin Srbu added a comment - - edited

          carlosruiz_globalqss
          I can't for my life find that setting. 
          Where is it??

           

          Nevermind! Found it!

          Still don't see any output though, just success or unstable.
          I'm downgrading till this is fixed. :-/

          Sorin Srbu added a comment - - edited carlosruiz_globalqss I can't for my life find that setting.  Where is it??   Nevermind! Found it! Still don't see any output though, just success or unstable. I'm downgrading till this is fixed. :-/
          Travis Abdelhamed made changes -
          Attachment New: image-2020-11-17-15-56-46-618.png [ 53379 ]

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

              Created:
              Updated:
              Resolved: