Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Inside a groovy script (for a jenkins pipeline): How can I run a bash command instead of a sh command?

I have tried the following:

Call " #!/bin/bash " inside the sh call:

stage('Setting the variables values') {
    steps {
         sh '''
            #!/bin/bash
            echo "hello world"
Replace the sh call with a bash call: 
stage('Setting the variables values') {
    steps {
         bash '''
            #!/bin/bash
            echo "hello world"
Additional Info:
My command is more complex than a echo hello world.
                What is your question ? Please formulate your question clearly and provide the problems details you are facing.
– deimus
                Jun 2, 2017 at 13:46
                I think we have the same problem. Even with the second example, it still executes with sh instead of bash. Is that what you are seeing?
– Jake
                Jul 19, 2017 at 1:51
                Yes, it is! A create a solution adding a .bash file on my git repository, so i speak to Jenkins run it on a specific path inside of my  project.
– Yago Azedias
                Jul 19, 2017 at 1:54
                Take a look at my answer to a similar question here: stackoverflow.com/a/57381691/10398126
– Quinn Vissak
                Aug 6, 2019 at 18:21
The Groovy script you provided is formatting the first line as a blank line in the resultant script. The shebang, telling the script to run with /bin/bash instead of /bin/sh, needs to be on the first line of the file or it will be ignored.
So instead, you should format your Groovy like this:
stage('Setting the variables values') {
    steps {
         sh '''#!/bin/bash
                 echo "hello world" 
And it will execute with /bin/bash.
                @Jake Any idea how you gen use a bash-specific script in a stage? This part works for me too, but when I try to trigger a bash script it does not work for me.
– DenCowboy
                Nov 24, 2017 at 12:48
                For multi-line scripts or those run multiple times, I would create a new bash script file (starting from #!/bin/bash), and simply run it with: chmod +x './script.sh' && sh './script.sh'
– mirekphd
                Dec 13, 2019 at 16:45
                The logo returns a error for the "+"  WorkflowScript: 9: illegal string body character after dollar sign;    solution: either escape a literal dollar sign "\$5" or bracket the value expression "${5}" @ line 9, column 68.    2c-437a-b8a2-db013fe42f62\"" +
– Yago Azedias
                Jun 2, 2017 at 18:23
                Can you please post the script? From what you've pasted, it looks like there are two quotes before the +, which is wrong.
– Jacob
                Jun 2, 2017 at 18:56
                Thank you @Jacob I was having the same problem and your comment helped me to solve those!
– Anuradha Fernando
                Jan 19, 2019 at 21:53
For multi-line shell scripts or those run multiple times, I would create a new bash script file (starting from #!/bin/bash), and simply run it with sh from Jenkinsfile: 
sh 'chmod +x ./script.sh'
sh './script.sh'
I'm sure that the above answers work perfectly. However, I had the difficulty of adding the double quotes as my bash lines where closer to 100. So, the following way helped me. (In a nutshell, no double quotes around each line of the shell)
Also, when I had "bash '''#!/bin/bash" within steps, I got the following error java.lang.NoSuchMethodError: No such DSL method '**bash**' found among steps
pipeline {
    agent none
    stages {
        stage ('Hello') {
            agent any
            steps {
                echo 'Hello, '
                sh '''#!/bin/bash
                    echo "Hello from bash"
                    echo "Who I'm $SHELL"
The result of the above execution is
If you want to change your default shell to bash for all projects on Jenkins, you can do so in the Jenkins config through the web portal:
Manage Jenkins > Configure System (Skip this clicking if you want by just going to https://{YOUR_JENKINS_URL}/configure.)
Fill in the field marked 'Shell executable' with the value /bin/bash and click 'Save'.
In my case, I had to execute a Shell script in bash via jenkinsfile. Here's what worked for me :
sh 'core_devops/automation/scripts/ecs_initialize.sh'
And the first line in the script had
#!/bin/bash
The problem is indeed that the shebang is ignored if it doesn't start at the very beginning of the file.
As an alternative to mangling the formatting for Jenkinsfile readers, I've taken to using this:
sh label: 'Run fancy bash script',
   script: '''
       #!/usr/bin/env  bash
       echo "Hello ${SHELL}!"
   '''.stripIndent().stripLeading()
Note that stripIndent() is not strictly necessary for it to work, but Jenkins logs are a lot nicer with it.
return "Hello /bin/sh"...
after some search I found "sh" was "dash" instead of bash on another terminal
Ubuntu22 :
jenkins@ubuntu22:~$ command -v sh
/usr/bin/sh
jenkins@ubuntu22:~$ ls -l /usr/bin/sh
lrwxrwxrwx 1 root root 4 Mar 23  2022 /usr/bin/sh -> dash
jenkins@ubuntu22:~$ command -v dash
/usr/bin/dash
on my old Red Hat 7.4 :
[jenkins@RH7.4 ~]$ command -v sh
/usr/bin/sh
[jenkins@RH7.4 ~]$ ls -l /usr/bin/sh
lrwxrwxrwx 1 root root 4 Sep  6  2018 /usr/bin/sh -> bash
[jenkins@RH7.4 ~]$ command -v bash
/usr/bin/bash
[jenkins@RH7.4 ~]$ ls -l /usr/bin/bash
-rwxr-xr-x 1 root root 960632 Aug  3  2017 /usr/bin/bash
        
Thanks for contributing an answer to Stack Overflow!
Please be sure to answer the question. Provide details and share your research!
But avoid …
Asking for help, clarification, or responding to other answers.
Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.