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

Shell script taking/returning output/status

    XMLWordPrintable

Details

    Description

      Currently sh has no meaningful return value, and throws an exception if the exit status is not zero. Would be nice to have an option to have it return the exit code (zero or not) as an integer value:

      def r = sh script: 'someCommand', returnStatus: true

      Current workaround:

      sh 'someCommand; echo $? > status'
def r = readFile('status').trim()

      Or to have it return its standard output (akin to shell backticks):

      def lines = sh(script: 'dumpStuff.sh', returnStdout: true).split("\r?\n")

      Workaround:

      sh 'dumpStuff.sh > result'
def lines = readFile('result').split("\r?\n")

      Or to have it take something on standard input:

      sh script: 'loadStuff.sh', stdin: someText

      Workaround:

      writeFile file: 'input', text: someText
sh 'loadStuff.sh < input'

      Probably requires some API changes in durable-task.

      Attachments

        Issue Links

          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-34331 get shell to expose a value

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-26812 Storing the shell script execution output in workflow

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-28302 Workflow steps should expose console output to script somehow

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-33173 Improve how to get output of sh execution

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-29877 failure when incorrect shell is configured is not clear enough to diagnose root cause.

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-27152 Store sh control files outside of workspace

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-44930 Allow sh to return exit status, stdout and stderr all at once

          • Major - Major loss of function.
          • Open
          links to

          Web Link PR 11

          Activity

            Ascending order - Click to sort in descending order
            View 20 older comments
            shott85 David Schott added a comment -

            Hi benji2006, there are other ways to provide a password besides stdin.

            Check out this example Jenkinsfile (apologies for weird formatting) and note the usage of Credentials & 'environment' in the "Build & Push Docker Image" stage.

            shott85 David Schott added a comment - Hi benji2006 , there are other ways to provide a password besides stdin. Check out this example Jenkinsfile (apologies for weird formatting) and note the usage of Credentials & 'environment' in the "Build & Push Docker Image" stage.
            benji2006 ben ji added a comment - - edited

            Hi shott85,

            this isn't a regular docker log in - in this particular scenario using Notary, it looks like the only way to pass in the required content is via stdin - there are no env variables that work - see the second update to this bug report:

             

            https://forums.docker.com/t/cannot-get-trust-delegation-to-work-notary-v0-3-0-solved/14370

            SECOND UPDATE:

            Looks as if I can supply the passphrase on standard input – seems to be working now.

             

             

            I can get the command to work outside Jenkins using 

            echo "delegationpass" | docker push .....

            and need to emulate that in my pipeline script

             

            benji2006 ben ji added a comment - - edited Hi shott85 , this isn't a regular docker log in - in this particular scenario using Notary, it looks like the only way to pass in the required content is via stdin - there are no env variables that work - see the second update to this bug report:   https://forums.docker.com/t/cannot-get-trust-delegation-to-work-notary-v0-3-0-solved/14370 SECOND UPDATE: Looks as if I can supply the passphrase on standard input – seems to be working now.     I can get the command to work outside Jenkins using  echo "delegationpass" | docker push ..... and need to emulate that in my pipeline script  
            jglick Jesse Glick added a comment -

            benji2006 please do not use JIRA as a help forum. There is a users’ list and other places to ask for help using Jenkins.

            jglick Jesse Glick added a comment - benji2006 please do not use JIRA as a help forum. There is a users’ list and other places to ask for help using Jenkins.
            drewish andrew morton added a comment -

            I went ahead and created https://issues.jenkins-ci.org/browse/JENKINS-44930 to focus on returning the exit status and standard output at the same time. So I hope all the folks who commented asking for this feature will go up vote that

            drewish andrew morton added a comment - I went ahead and created https://issues.jenkins-ci.org/browse/JENKINS-44930  to focus on returning the exit status and standard output at the same time. So I hope all the folks who commented asking for this feature will go up vote that
            visxu Vision Xu added a comment -

             

            Code:

            def output = sh( 
    script: """cd ${component_root_path} && JAVA_HOME=${JAVA_HOME} mvn dependency:list -Dsort=true""", 
    returnStdout: true
)

             

             

            But Get no output.

            [Pipeline] echo
[12-22 22:18:28] output:
            visxu Vision Xu added a comment -   Code: def output = sh( script: """cd ${component_root_path} && JAVA_HOME=${JAVA_HOME} mvn dependency:list -Dsort= true " "", returnStdout: true )     But Get no output. [Pipeline] echo [12-22 22:18:28] output:

            People

              jglick Jesse Glick
              jglick Jesse Glick
              Votes:
              50 Vote for this issue
              Watchers:
              65 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: