Jenkins build step execute shell marked build as failure

First things first, hover the mouse over the grey area below. Not part of the answer, but absolutely has to be said:

Índice Show

Jenkins Build step'Execute shell' marked build as failure
How do I run a shell in Jenkins?
How do you mark as fail in Jenkins?
What does #!/ Bin sh do?
Why do we use #!/ Bin bash in the beginning of a script?

If you have a shell script that does "checkout, build, deploy" all by itself, then why are you using Jenkins? You are foregoing all the features of Jenkins that make it what it is. You might as well have a cron or an SVN post-commit hook call the script directly. Jenkins performing the SVN checkout itself is crucial. It allows the builds to be triggered only when there are changes (or on timer, or manual, if you prefer). It keeps track of changes between builds. It shows those changes, so you can see which build was for which set of changes. It emails committers when their changes caused successful or failed build (again, as configured as you prefer). It will email committers when their fixes fixed the failing build. And more and more. Jenkins archiving the artifacts also makes them available, per build, straight off Jenkins. While not as crucial as the SVN checkout, this is once again an integral part of what makes it Jenkins. Same with deploying. Unless you have a single environment, deployment usually happens to multiple environments. Jenkins can keep track of which environment a specific build (with specific set of SVN changes) is deployed it, through the use of Promotions. You are foregoing all of this. It sounds like you are told "you have to use Jenkins" but you don't really want to, and you are doing it just to get your bosses off your back, just to put a checkmark "yes, I've used Jenkins"

The short answer is: the exit code of last command of the Jenkin's Execute Shell build step is what determines the success/failure of the Build Step. 0 - success, anything else - failure. Note, this is determining the success/failure of the build step, not the whole job run. The success/failure of the whole job run can further be affected by multiple build steps, and post-build actions and plugins.

You've mentioned Build step 'Execute shell' marked build as failure, so we will focus just on a single build step. If your Execute shell build step only has a single line that calls your shell script, then the exit code of your shell script will determine the success/failure of the build step. If you have more lines, after your shell script execution, then carefully review them, as they are the ones that could be causing failure.

Finally, have a read here Jenkins Build Script exits after Google Test execution. It is not directly related to your question, but note that part about Jenkins launching the Execute Shell build step, as a shell script with /bin/sh -xe

The -e means that the shell script will exit with failure, even if just 1 command fails, even if you do error checking for that command (because the script exits before it gets to your error checking). This is contrary to normal execution of shell scripts, which usually print the error message for the failed command (or redirect it to null and handle it by other means), and continue.

To circumvent this, add set +e to the top of your shell script.

Since you say your script does all it is supposed to do, chances are the failing command is somewhere at the end of the script. Maybe a final echo? Or copy of artifacts somewhere? Without seeing the full console output, we are just guessing.

Please post the job run's console output, and preferably the shell script itself too, and then we could tell you exactly which line is failing.

Jenkins Build step'Execute shell' marked build as failure

Questions are as follows:

View Image

solution:

Modify configure
execute shell command, add: #!/bin/bash
View Image

explain in detail

When running the script when Jenkins builds an error: Build step'Execute shell' marked build as failure
Possible reasons:
1. An error is reported due to insufficient disk space.
2. Please add in the "Execute shell (execute shell)" build step command: #!/bin/bash
Generally, by default, Jenkins adopts/bin/sh -xe this way -x will print each command; another Option -e, when any command exits the code with a non-zero value (when any command fails), this will cause the shell to immediately stop running the script, and #!/bin/bash means that this script uses/bin/bash to explain the execution

Note 1: #! is a special indicator, which means the shell path to explain this script.
Note 2: Bash is just a kind of shell, and there are many other shells, such as sh, csh. . Etc.
Note 3: #!/bin/bash can only be placed on the first line, if there is #! after it, it can only be regarded as a comment

How do I run a shell in Jenkins?

Your answer.

Create a freestyle project on Jenkins..

Use the advanced configuration page to use custom workspace..

Add the path to your shell script..

Under the build step, select "execute shell".

Finally, enter the name of your shell script and click on save and execute it..

How do you mark as fail in Jenkins?

The default setting in Jenkins is to mark a job yellow, when a Maven build fails because of failing tests..

Go to Manage Jenkins -> Manage system..

Add -Dmaven. test. failure. ... .

Save this change and that's it..

What does #!/ Bin sh do?

#!/bin/sh: It is used to execute the file using sh, which is a Bourne shell, or a compatible shell. #!/bin/csh: It is used to execute the file using csh, the C shell, or a compatible shell. #!/usr/bin/perl -T: It is used to execute using Perl with the option for taint checks.

Why do we use #!/ Bin bash in the beginning of a script?

#!/bin/bash Essentially it tells your terminal that when you run the script it should use bash to execute it. It can be vital since you may be using a different shell in your machine ( zsh , fish , sh , etc.), but you designed the script to work specifically with bash.