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

[jira-importer]

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.

---

Originally reported by malice00, imported from: Publish over SSH log the output of the exec global option

• status: Open
• priority: Major
• resolution: Unresolved
• imported: 2022/01/10

[jira-importer]

carlosruiz_globalqss:

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

 

[jira-importer]

malice00:

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

[jira-importer]

carlosruiz_globalqss:

Thanks Roland Asmann.

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.

 

 

 

[jira-importer]

awinlei:

Carlos Ruiz 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

[jira-importer]

carlosruiz_globalqss:

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

[jira-importer]

emka:

Thanks Roland Asmann. 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.

[jira-importer]

jdbeckerle:

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.

[jira-importer]

JIRAUSER130237:

Carlos Ruiz
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. :-/

[jira-importer]

porkrines42:

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

 

[jira-importer]

timja:

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

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

[jira-importer]

slide_o_mix:

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.

[jira-importer]

JIRAUSER130237:

Travis Abdelhamed

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.
 
 

[jira-importer]

[Originally related to: JENKINS-65170]

[jiteshgolecha]

How can i enable Verbose output option in latest version?