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

Option to disable echo of executed commands

XMLWordPrintable

      Please add an option to disable echo of the command being executed (echo to log).

      Most of the time the commands only make the log less clear to read and harder to inspect.

      Current workaround is to put commands in a script and just execute the script. This however is not a viable workaround in all cases.

          [JENKINS-33455] Option to disable echo of executed commands

          Maciej Jaros created issue -

          Maciej Jaros added a comment -

          BTW for standard "Execute shell" step there is a better workaround - you can simply add `set +x` command to disable echo. However this doesn't work for the SSH plugin.

          Maciej Jaros added a comment - BTW for standard "Execute shell" step there is a better workaround - you can simply add `set +x` command to disable echo. However this doesn't work for the SSH plugin.
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 169375 ] New: JNJira + In-Review [ 183474 ]

          Rachel M. added a comment -

          I got it with:

          #!/bin/bash +x

          Rachel M. added a comment - I got it with: #!/bin/bash +x
          Alex Earl made changes -
          Assignee Original: bap [ bap ] New: Alex Earl [ slide_o_mix ]

          Alex Earl added a comment -

          It looks like there is already a workaround for this, I would recommend using that workaround.

          Alex Earl added a comment - It looks like there is already a workaround for this, I would recommend using that workaround.
          Alex Earl made changes -
          Resolution New: Done [ 10000 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          david ducker added a comment -

          I agree this makes logs so much harder to read with no added value.
          Unless I'm mistaken you would have to set +x for every single shell, some of my scripts have 100's. This is not an adequate workaround.

          david ducker added a comment - I agree this makes logs so much harder to read with no added value. Unless I'm mistaken you would have to set +x for every single shell, some of my scripts have 100's. This is not an adequate workaround.

          Maciej Jaros added a comment - - edited

          rachel are you sure you are using SSH plugin? That is are you using "Send files or execute commands over SSH"? I tried your workaround and it doesn't work for SSH step. It only works for "Execute shell" step which is not what the task is about.

          Maciej Jaros added a comment - - edited rachel are you sure you are using SSH plugin? That is are you using "Send files or execute commands over SSH"? I tried your workaround and it doesn't work for SSH step. It only works for "Execute shell" step which is not what the task is about.

          Rachel M. added a comment -

          Hi nux, which Operating System is Jenkins running on?

          Rachel M. added a comment - Hi nux , which Operating System is Jenkins running on?

            Unassigned Unassigned
            nux Maciej Jaros
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: