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

            carlosruiz_globalqss 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  
            malice00 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??

            malice00 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??
            carlosruiz_globalqss 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.

             

             

             

            carlosruiz_globalqss 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.      
            awinlei 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

            awinlei 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
            carlosruiz_globalqss 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.

            carlosruiz_globalqss 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.
            emka 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.

            emka 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.
            jdbeckerle 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.

            jdbeckerle 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 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 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. :-/

            For anyone not wanting to waste a few aggravating minutes of finding the setting, see screenshots below:

             

            porkrines42 Travis Abdelhamed added a comment - For anyone not wanting to waste a few aggravating minutes of finding the setting, see screenshots below:  
            timja Tim Jacomb added a comment -

            porkrines42 does configuring the option work for you? as the previous user said it didn't work for them

            cc slide_o_mix who made the change originally (and didn't release it at the time :sad

            timja Tim Jacomb added a comment - porkrines42 does configuring the option work for you? as the previous user said it didn't work for them cc slide_o_mix who made the change originally (and didn't release it at the time :sad
            slide_o_mix Alex Earl added a comment -

            I don't even recall why this change was made...I think at the time most people were asking for LESS log output, so the change was put in. I didn't realize it didn't get released.

            slide_o_mix Alex Earl added a comment - I don't even recall why this change was made...I think at the time most people were asking for LESS log output, so the change was put in. I didn't realize it didn't get released.
            sorin_srbu Sorin Srbu added a comment -

            porkrines42

            Thank you!
            Turns out it wasn't the the verbose-setting in Manage Jenkins I found that had to checked.

            I now have verbose output even with the new plugin version, although I'm too happy having to check it on all my jobs.
             
             

            sorin_srbu Sorin Srbu added a comment - porkrines42 Thank you! Turns out it wasn't the the verbose-setting in Manage Jenkins I found that had to checked. I now have verbose output even with the new plugin version, although I'm too happy having to check it on all my jobs.    

            For your information, all publish-over-ssh component type JENKINS issues related to the Publish Over SSH plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues

            Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues/79
            And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-ssh-plugin/issues?q=%22JENKINS-64101%22

            (Note: this is an automated bulk comment)

            gmcdonald Gavin McDonald added a comment - For your information, all publish-over-ssh component type JENKINS issues related to the Publish Over SSH plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues/79 And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-ssh-plugin/issues?q=%22JENKINS-64101%22 (Note: this is an automated bulk comment)

            Closing ticket, please use the corresponding Github Issue as linked above.

            gmcdonald Gavin McDonald added a comment - Closing ticket, please use the corresponding Github Issue as linked above.

            People

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

              Dates

                Created:
                Updated:
                Resolved: