Micah Anderson
2009-May-31 14:55 UTC
[Cruisecontrolrb-users] Builds failing but not being reported as failed
I''ve got a build for a project that clearly has failures in the
build.log, but shows up as a successful build in cruise (and the RSS
feed). I''m trying to determine what is causing this and how to get
those
builds to show up as failed.
I have a build.sh, which performs the different steps for building,
pretty basic stuff, it looks like this:
#!/bin/sh
export RAILS_ENV=test
patch -p1 < ../greencloth.diff
echo "loading default schema"
rake db:schema:load
echo "running rake db:test:prepare..."
rake db:test:prepare
echo "running rake db:fixtures:load..."
rake db:fixtures:load
echo "running rake ts:index..."
rake ts:index
echo "running rake ts:start..."
rake ts:start
echo "running rake test:functionals..."
rake test:functionals
echo "running rake test..."
rake test
echo "running rake test:tools:all..."
rake test:tools:all
echo "running rake test:units:rcov..."
rake test:units:rcov
if [ -d $CC_BUILD_ARTIFACTS ]
then
echo "moving unit test coverage build artifacts to the proper
place..."
mv coverage/units $CC_BUILD_ARTIFACTS/unit_test_coverage
fi
export SHOW_ONLY=controllers
echo "running test:functionals:rcov..."
rake test:functionals:rcov
if [ -d $CC_BUILD_ARTIFACTS ]
then
echo "moving functional test coverage artifacts to the proper
place..."
mv coverage/functionals
$CC_BUILD_ARTIFACTS/functional_test_coverage
fi
echo "running rake test:integration..."
rake test:integration
A failed build, that did not get reported as failed, can be seen at
http://labs.riseup.net:3333/builds/crabgrass/eaa4d1
Any help would be appreciated!
micah
Chris Roos
2009-Jun-01 12:57 UTC
[Cruisecontrolrb-users] Builds failing but not being reported as failed
I think I''m right in saying that you need your script to exit with a non 0 status in order to let cruise know that the build failed. I''m guessing that, although you have test failures, your script is still exiting with a 0 status. Chris On Sun, May 31, 2009 at 3:55 PM, Micah Anderson <micah at riseup.net> wrote:> > I''ve got a build for a project that clearly has failures in the > build.log, but shows up as a successful build in cruise (and the RSS > feed). I''m trying to determine what is causing this and how to get those > builds to show up as failed. > > I have a build.sh, which performs the different steps for building, > pretty basic stuff, it looks like this: > > #!/bin/sh > > export RAILS_ENV=test > patch -p1 < ../greencloth.diff > > echo "loading default schema" > rake db:schema:load > > echo "running rake db:test:prepare..." > rake db:test:prepare > > echo "running rake db:fixtures:load..." > rake db:fixtures:load > > echo "running rake ts:index..." > rake ts:index > > echo "running rake ts:start..." > rake ts:start > > echo "running rake test:functionals..." > rake test:functionals > > echo "running rake test..." > rake test > > echo "running rake test:tools:all..." > rake test:tools:all > > echo "running rake test:units:rcov..." > rake test:units:rcov > if [ -d $CC_BUILD_ARTIFACTS ] > then > ? ? ? ?echo "moving unit test coverage build artifacts to the proper > ? ? ? ?place..." > ? ? ? ?mv coverage/units $CC_BUILD_ARTIFACTS/unit_test_coverage > fi > > export SHOW_ONLY=controllers > echo "running test:functionals:rcov..." > rake test:functionals:rcov > > if [ -d $CC_BUILD_ARTIFACTS ] > then > ? ? ? ?echo "moving functional test coverage artifacts to the proper > ? ? ? ?place..." > ? ? ? ?mv coverage/functionals > ? ? ? ?$CC_BUILD_ARTIFACTS/functional_test_coverage > fi > > echo "running rake test:integration..." > rake test:integration > > A failed build, that did not get reported as failed, can be seen at > http://labs.riseup.net:3333/builds/crabgrass/eaa4d1 > > Any help would be appreciated! > micah > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >-- http://chrisroos.co.uk
Micah Anderson
2010-Mar-11 15:34 UTC
[Cruisecontrolrb-users] Builds failing but not being reported as failed
Ooops, I failed to see this follow-up message:> Did this solve your problem, Micah?In fact it did! Thanks! :) micah -- "It is no measure of health to be well adjusted to a profoundly sick society." - J Krishnamurti -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20100311/ac8210de/attachment.bin>