• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • hashicorp-vault-plugin
    • None
    • Jenkins ver. 1.480.1
      Linux/Cent OS
      vault 2.1.0

      When configuring a Post-build Action to execute a shell script ("Batch or a shell script files to execute"), the output from the script is not displayed. If the script is added as a Build step (still Post-build Action), the output is displayed.

      If this is intended behavior, maybe the "Batch or a shell script files to execute" option should have a check box "Display output from script"?

          [JENKINS-15912] Shell script files output is not displayed

          Strange behavior.
          I tested it and it should be fixed for now.
          Do not hesitate to reopen it with more explanations if the issue persists.

          Gregory Boissinot added a comment - Strange behavior. I tested it and it should be fixed for now. Do not hesitate to reopen it with more explanations if the issue persists.

          Vaclav Adamec added a comment -

          Strikes back with actual versions:
          Jenkins ver. 2.103
          Plugin ver. 2.1.0

          with enabled Vault there is no shell output after git checkout processing

          Vaclav Adamec added a comment - Strikes back with actual versions: Jenkins ver. 2.103 Plugin ver. 2.1.0 with enabled Vault there is no shell output after git checkout processing

          Daniel Heid added a comment -

          Could you please provide more input? Job configuration, console output, ...

          Daniel Heid added a comment - Could you please provide more input? Job configuration, console output, ...

          Vaclav Adamec added a comment - - edited

          Build config (xml) https://gist.github.com/VAdamec/5d47046ae60f86f30667df7cc27e723e

          in output is just SCM, git, then nothing (but job is running)

           

          00:00:00.777 > git config core.sparsecheckout # timeout=10
          00:00:00.779 > git checkout -f 575982de60be9a336b517034ca99cf4e8b6f4a17
          00:00:00.793 Commit message: "Test"
          00:00:00.795 > git rev-list --no-walk 575982de60be9a336b517034ca99cf4e8b6f4a17 # timeout=10 00:00:00.804 Set build name.
          00:00:00.806 New build name is '#38-'

          and then nothing till playbook finish. Without Vault plugin it works without any problem.

          Vaclav Adamec added a comment - - edited Build config (xml) https://gist.github.com/VAdamec/5d47046ae60f86f30667df7cc27e723e in output is just SCM, git, then nothing (but job is running)   00:00:00.777 > git config core.sparsecheckout # timeout=10 00:00:00.779 > git checkout -f 575982de60be9a336b517034ca99cf4e8b6f4a17 00:00:00.793 Commit message: "Test" 00:00:00.795 > git rev-list --no-walk 575982de60be9a336b517034ca99cf4e8b6f4a17 # timeout=10 00:00:00.804 Set build name. 00:00:00.806 New build name is '#38-' and then nothing till playbook finish. Without Vault plugin it works without any problem.

          Daniel Heid added a comment -

          Thanks! I can't find any postbuildscript steps in the provided job configuration. They should appear in the publishers section. Removed postbuildscript from the components.

          Daniel Heid added a comment - Thanks! I can't find any postbuildscript steps in the provided job configuration. They should appear in the publishers section. Removed postbuildscript from the components.

            rakeshsingh99 Rakesh Singh
            mabahj Markus
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: