tags:

views:

363

answers:

2

I've got a build script from a 3rd party tool. It does it's job properly, but throws a useless exception at the end which I need to ignore.

But Hudson doesn't ignore it. It stops my build when this script exits with an error code != 0. Which it does, even when the last line is 'exit 0'.

There is no option in the Hudson build configuration to specify how to treat failure of a particular build step.

Is there a hidden option to tell Hudson to soldier on? Where is the general reference for Hudson's config.xml?

+1  A: 

One of Hudson's key properties is that everything can be configured via the web interface. So looking at the config.xml is not the right approach.

In Hudson, your windows command can be launched via a batch file. I suggest looking into making that batch file return a zero error code, regardless of what your third party tool does. The first line would invoke your tool, and the second line would be 'exit 0'

Michael Donohue
From the question:"Which it does, even when the last line is 'exit 0'"But you're right, there isn't an option to tell hudson to ignore an error on a particular build step. And thanks for the tip about it's all on the web. I won't waste any more time looking for hidden features.
Sean Cavanagh
A: 

Seems that one has to wrap the offending script in it's own bat:

copy con wrapper.bat
>myErrorMakingScript.bat
>exit /b 0

and then fire wrapper.bat from Hudson.

Sean Cavanagh

related questions