The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Grails Clover plugin - Bamboo looks in wrong directory for Clover results

Will Dampney
January 4, 2015

Using plugin clover:4.0.2 with Grails 2.3.7, Bamboo 5.3

 

When clover is enabled (i.e. Awhile the plugin writes the report to target\clover.

Setting the configuration option in BuildConfig.groovy reportdir seems to have no effect:

// Clover plugin configuration
clover {
    on = true
    reportdir = "target/site/clover"  // Because Bamboo looks here, and default is target/clover
    directories = ['src/java', 'src/groovy', 'test/unit', 'test/integration', 'grails-app']
    includes = ['**/*.groovy', '**/*.java']
    excludes = ['**/conf/**', '**/plugins/**', '**/migrations/**']
    json = true
    title = "${appName} ${appVersion} (Grails ${grailsVersion})"
}

 

How do I make them both use the same directory?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Will Dampney
January 4, 2015

It appears that the automatic configuration overrides the reportdir I set, and reverts to the default target\clover. I suppose this is intended behaviour, but the grails plugin should be pointing to the same report directory by default.

Setting the build to Clover is already integrated into this build... and modifying the XML location works, ensuring that the on option is set to 'true'. Simplified config now looks like:

clover {
    on = true
    includes = ['**/*.groovy', '**/*.java']
    excludes = ['**/conf/**', '**/plugins/**', '**/migrations/**']
    json = true
    title = "${appName} ${appVersion} (Grails ${grailsVersion})"
}
TAGS
AUG Leaders

Atlassian Community Events