We are having problems with CruiseControl.Net 1.5.7256.1. Our construction is successful, when they are actually failing, we force construction, this unit runs the tests, the trial of some units fails and it shows success successfully that we can execute an exec Are using the work. Here's the goal of performing the test:
& lt; Target name = "test" dependent = "build" description = "unit test" & gt;
& lt; Copy file = "configuration_notag.txt" tofile = "$ {build.dir} \ configuration.txt" />
& lt; Junit errorProperty = "test.failed" failureproperty = "test.fail" & gt;
& lt; Formatter type = "abbreviated" usefile = "false" />
& lt; Formatter type = "xml" />
& lt; Classpath refid = "classpath" />
& lt; Test name = "$ {test1.class}" />
& lt; Test name = "$ {test2.class}" />
& lt; / Junit & gt;
& lt; Fail message = "test failed: check test report." If = "test.failed" /> gt;
& lt; / Target & gt;
Here the output file is given in the build file:
Errors: (4) [Janit] Test Test Notable Failure Created C: \ Sandbox \ Idblue \ idblue \ trunk \ Unit_Test \ IDBlueJavaWindowsUnitTest \ build_notag.xml: 43: Test Failure: Check the Inquiry Report. Total time: 2 mins 37 seconds
Since the ant is failing, a failure error code is returning, why is not the cruise control picking it up? There is nothing to note in our ccnet.config file, it just calls AT with proper build file. We did not have this problem with Cruise ControlOnit 1.4.2. Has anyone else gone to this issue? The problem was misguided but nothing was found.
I found out what was the problem, I needed to add it to the last line of Ant.bat :
Exit% ERRORLEVEL%
It returned the acent code to the cruise control and the build finally failed properly.
Comments
Post a Comment