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

Will Dampney2

Using plugin clover:4.0.2 with Grails 2.3.7, Bamboo 5.3

 

When clover is enabled (i.e. Automatically integrate Clover into this build), Bamboo looks to target\site\clover while 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?

Will Dampney2

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 <span>Clover is already integrated into this build... and modifying the&nbsp;</span>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})"
}