CTest returning non-zero error code should not stop the build

Details

Description

If a test fails then CTest returns a non-zero return code (8 in my configuration) and jenkins build is stopped.
This makes the build fail even if higher unstable and fail thresholds are selected.
An option to select the return code to be ignored will work the best.

Yes, adding an option to ignore the exit status would do the job in my case.
On the other side, it can be that CTest returns a different error code if there is another kind of error (wrong parameters, etc.). That kind of errors shouldn't be ignored. Unfortunately the CTest documentation does not specifies the error codes.

Dragos Carp
added a comment - 2016-06-16 20:44 - edited Yes, adding an option to ignore the exit status would do the job in my case.
On the other side, it can be that CTest returns a different error code if there is another kind of error (wrong parameters, etc.). That kind of errors shouldn't be ignored. Unfortunately the CTest documentation does not specifies the error codes.

Martin Weber
added a comment - 2016-06-20 20:15 Please try https://jenkins.ci.cloudbees.com/job/plugins/job/cmakebuilder-plugin/org.jenkins-ci.plugins$cmakebuilder/102/artifact/org.jenkins-ci.plugins/cmakebuilder/2.4.3-SNAPSHOT/cmakebuilder-2.4.3-SNAPSHOT.hpi and provide some feedback.
My unittests are unreliable here, since ctest v. 2.8.11.2 seems to always exit with success so they never fail for this issue .
And please have a look at the online help and send suggestions, as I am not a native speaker.

Unfortunately it didn't work out as expected. Actually even that the Plugin Manager shows that "CMake plugin 2.4.3-SNAPSHOT (private-e95ede2f-jenkins)" is installed, I couldn't find any option to disable the checking of the exit code. Currently I'm using Jenkins 2.5 installed on Windows 2008 Server.
The relevant section in the "Console Output":