How can I get Hudson to continue building after a Windows command crashes?

Question

I have a build script from a third-party tool. He does it right, but throws a useless exception at the end, which I need to ignore.

But Hudson does not ignore this. It stops my build when this script exits with an error code! = 0. What does it do even if the last line is "exit 0".

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

Is there a hidden option to tell Hudson a soldier? Where is the generic link for Hudson config.xml?

Answer 1

It seems like you need to wrap the abusive script in your own bat:

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

fire wrapper.bat Hudson.

Answer 2

Unix , bash, - " 0". :

bash -c "false; exit 0"

"false", 0.

, . , .

Answer 3

, -. config.xml .

In Hudson, your windows command can be run through a batch file. I suggest exploring that a batch file returns a zero error code, regardless of what your third-party tool does. The first line will call your tool, and the second line will be "exit 0"

Answer 4

Using a plugin trigger Plugin works fine for me. check out “Trigger even if some downstream projects are unstable”