Question

I’m barely started to use Jenkins and this is the first problem I’ve had so far. Basically my jenkins job always succeed even when an error happened in some of the tests. This is what I’m running in the shell config:

bundle install 
rake db:migrate:reset
rake test:units
rake spec:models

Thing is that Jenkins only reports a failure when the task which fails is the last one. For instance, if I put “rake test:units” the last task it will notify an error if something go wrong. Using this configuration I only get error reports for the rspec tests but not for the unit tests.

Anyone wondering why I don’t only use rspec or unit test, we are currently migrating to rspec but this problem is still painful.

This is part of the log from Jenkinsm as you can see one of the unit test fails but jenkins still finish with success.

314 tests, 1781 assertions, 1 failures, 0 errors, 0 skips
rake aborted!
Command failed with status (1): [/var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p1...]

Tasks: TOP => test:units
(See full trace by running task with --trace)
Lot of rspec tests here....
Finished in 3.84 seconds
88 examples, 0 failures, 42 pending
Pushing HEAD to branch master of origin repository
Pushing HEAD to branch master at repo origin
Finished: SUCCESS

Answer 1

Jenkins executes the commands you type into a Build Step box by writing them to a temporary file and then running the script using /bin/sh -xe.

Usually this produces the desired effect: Commands are executed in sequence (and printed) and the script aborts immediately when a command fails i.e. exits with non-zero exit code.

If this is not happening to you, the only reason can be that you have overridden this behavior. You can override it by starting the first line of your Build Step with these two characters: #!.

For example, if your Build Step looks like this:

#!/bin/bash
bundle install
rake db:migrate:reset
rake test:units
rake spec:models

Then it means Jenkins will write the script to a temporary file and it will be executed with /bin/bash. When invoked like that, bash will execute commands one-by-one and not care if they succeed. The exit code of the bash process will be the exit code of the last command in the script and that will be seen by Jenkins when the script ends.

So, take care in what you put on the first line of the Build Step. If you do not know how shell works, do not put a hash-bang at all and let Jenkins decide how the script should be run.

If you need more control over how the Build Step is executed, you should study the man page of the shell you use to find out how to make it behave the way you want. Jenkins doesn’t have much of a role in here. It just executes the shell you wanted the way you wanted.