Details
-
Type:
Improvement
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: publish-over-ssh-plugin
-
Labels:None
-
Environment:Jenkins 2.249.2
Publish over SSH 1.21
-
Similar Issues:
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
Activity
For anyone not wanting to waste a few aggravating minutes of finding the setting, see screenshots below:
Travis Abdelhamed
added a comment - For anyone not wanting to waste a few aggravating minutes of finding the setting, see screenshots below:
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
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.
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.
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. :-/