• Community
  • Questions
  • failure while using bamboo with automatic clover integration in a multi module maven project

failure while using bamboo with automatic clover integration in a multi module maven project


I have a parent project with a few child projects that I am trying to report on test coverage after the mvn clean test goals are executed in CI through bamboo.

The problem I am seeing is triggered when I enable clover history in bamboo, it manifests as the following:

12-Jul-2012 11:51:06 [INFO] Reactor Summary:
12-Jul-2012 11:51:06 [INFO]
12-Jul-2012 11:51:06 [INFO] Parent for the my-project projects ........... SUCCESS [6.288s]
12-Jul-2012 11:51:06 [INFO] my-project-shared ............................ FAILURE [1.107s]
12-Jul-2012 11:51:06 [INFO] my-project-a ........................ SUCCESS [17.508s]
12-Jul-2012 11:51:06 [INFO]my-project-b ....... SUCCESS [1.933s]
12-Jul-2012 11:51:06 [INFO] my-project-c ........................ SUCCESS [1.973s]
12-Jul-2012 11:51:06 [INFO] my-project-d ................ SUCCESS [2.032s]
12-Jul-2012 11:51:06 [INFO] ------------------------------------------------------------------------
12-Jul-2012 11:51:06 [INFO] BUILD FAILURE
12-Jul-2012 11:51:06 [INFO] ------------------------------------------------------------------------
12-Jul-2012 11:51:06 [INFO] Total time: 42.652s
12-Jul-2012 11:51:06 [INFO] Finished at: Thu Jul 12 11:51:06 EDT 2012
12-Jul-2012 11:51:06 [INFO] Final Memory: 126M/769M
12-Jul-2012 11:51:06 [INFO] ------------------------------------------------------------------------
12-Jul-2012 11:51:06 [ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-clover2-plugin:3.1.6:clover (default-cli) on project my-project-shared: Execution default-cli of goal com.atlassian.maven.plugins:maven-clover2-plugin:3.1.6:clover failed: java.lang.IllegalStateException: basedir /data/bamboo-home/xml-data/build-dir/131073/MY-PROJECTSNAP-JOB1/my-project-shared/.cloverhistory is not a directory -> [Help 1]

The project structure is somehing like this:






The build runs fine if i disable clover history, i actually see the colver report generated, but it fails at the end with that error. Is this the expected error if you have more than one agent? i wasn't so concerned with full consistency but some level of history would be nice. If this is not achievable I could force it to use only one agent.

I am only using a default-job (very simple) that has a svn checkout task and then a maven 3 task that simply does mvn clean test.

Thanks for any info on this!

2 answers

0 vote


I suggest raising a ticket at support.atlassian.com in Bamboo (BSP) or Clover (CLV) project. First, you can have a chance to get much faster response (due to SLA). Second, your problem looks to be more project/environment-specific so you could freely attach build files, logs and other potentially sensitive data on Support page (due to Atlassian privacy policy).


Thanks, I did the setup as described in that article and it took me further, but now I am getting a weird error that appears to have to do with having clover in the runtime given the setup as the article describes, here is the error I am getting:

java.lang.NoClassDefFoundError: com_cenqua_clover/CoverageRecorder

Update: the NoClassDefFoundError related with automatic Clover integration has been fixed in Bamboo 5.9 (https://jira.atlassian.com/browse/BAM-13208).

Suggest an answer

Log in or Join to answer
Community showcase
Maarten Cautreels
Posted Thursday in Off-topic

Friday Fun: What's your favourite beer/drink

As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...

369 views 39 10
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot