hdockter wrote:
> 
> You can specify the test results directory in Bamboo under Project/ 
> Plan/Configuration/Builder/ . You have to select that the build  
> produces test-results and where the test-results directories live.  
> There could specify something like: build/test-results/*.xml
> 
> - Hans
> 

Thank you Hans, it does work if I enter the right settings. Default value in
Bamboo is "**/test-reports/*.xml" as with default Gradle it would be
"**/test-results/*.xml".
So it was on Bamboo side, sorry for being so stupid, hopefully other people
like me will find the info by searching the mailing list.

@ james Bromley
So it's the /build/test-results/ folder that contains the info about tests,
if you leave default Gradle values.




> On Feb 4, 2009, at 3:56 PM, Rwanou wrote:
> 
>>
>> Hi all,
>>
>> I have seen on Gradle's project page that you can use Bamboo with  
>> gradle
>> along with the wrapper. If tried it my self quite sucessfully, but...
>> I cannot get Bamboo to recognize my tests. Here's the log output
>>
>> Executing build SAMPLEPRJ-BUILD-22
>>      Running pre-build action: Build Number Stamper
>>      Running pre-build action: VCS Version Collector
>>      Building started with ScriptBuilder
>>      
>> Starting to build 'Sampe Project - SancoLex - Simple build and test'
>> ... running command line: /bin/sh ./gradlew clean test
>> ... in : /home/sanco/bamboo-home/xml-data/build-dir/SAMPLEPRJ-BUILD
>> ... using java: null
>> ... using environment variables:
>> JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun-1.5.0.16
>>      :clean
>>      :init
>>      :resources
>>      :compile
>>      Note: Some input files use or override a deprecated API.
>>      Note: Recompile with -Xlint:deprecation for details.
>>      Note: Some input files use unchecked or unsafe operations.
>>      Note: Recompile with -Xlint:unchecked for details.
>>      :testResources
>>      :testCompile
>>      :test
>>      [ant:junit] Test sancolex.DefaultRandomTest FAILED
>>
>>      Build failed with an exception.
>>      Run with -s or -d option to get more details. Run with -f option to  
>> get
>> the full (very verbose) stacktrace.
>>      
>>      Build file
>> '/home/sanco/bamboo-home/xml-data/build-dir/SAMPLEPRJ-BUILD/ 
>> build.gradle'
>>
>>      Execution failed for task :test.
>>      Cause: There were failing tests. See the report at
>> /home/sanco/bamboo-home/xml-data/build-dir/SAMPLEPRJ-BUILD/build/ 
>> reports/tests.
>>      
>>      BUILD FAILED
>>      
>>      Total time: 17.796 secs
>>      Build process for 'Sampe Project - SancoLex - Simple build and test'
>> returned with return code = 1
>>      Running post build plugin 'Clover Results Collector'
>>      Running post build plugin 'Artifact Copier'
>>      Finalising the build...
>>      Stopping timer.
>>      Build SAMPLEPRJ-BUILD-22 completed.
>>      Running post build plugin on server 'Clover Delta Calculator'
>>
>>
>> so Bamboo sees that the build fails, and goes red (and whenever  
>> tests pass,
>> Bamboo goes green), but I'm unable to see the tests that failed.
>>
>> Does anybody have any experience with running Bamboo and Gradle  
>> together?
>>
>> Thanks in advance
>> -- 
>> View this message in context:
>> http://www.nabble.com/gradle-in-Bamboo-tp21833334p21833334.html
>> Sent from the gradle-user mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
> 
> --
> Hans Dockter
> Gradle Project lead
> http://www.gradle.org
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/gradle-in-Bamboo-tp21833334p21834072.html
Sent from the gradle-user mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to