I have done a bit of Googling in this area and have found many discussions about getting Jenkins to understand boost.test\'s XML output format, but no canonical reference. <
run_test --log_format=XML --log_sink=results.xml --log_level=all --report_level=no --result_code=no
I've added a parameter to Dave Bacher's answer because apparently Boost Test was using a non-zero exit code to indicate a test failure but Jenkins was interpreting this as a more fundamental failure, and thus stopping without processing the test results.
exit 201
Build step 'Execute Windows batch command' marked build as failure`