No Clover report in multi-module maven project

Hi All,

Our project is a multi-module maven project. I have created a new stage to execute Clover (according to the last question of troubleshooting section in Enabling the Clover add-on), but seems like Clover expects a standard maven project:

build	05-Mar-2015 20:44:55	[WARNING] The reported language of this project is none, attempting to instrument sources anyway.
build	05-Mar-2015 20:44:55	[INFO] No Clover instrumentation done on source files in: [/opt/bamboo/agent1/xml-data/build-dir/XXX-FORK6-CR/src/main/java] as no matching sources files found (JAVA_LANGUAGE)
build	05-Mar-2015 20:44:55	[INFO] No Clover instrumentation done on source files in: [/opt/bamboo/agent1/xml-data/build-dir/XXX-FORK6-CR/src/test/java] as no matching sources files found (JAVA_LANGUAGE)
build	05-Mar-2015 20:44:56	[WARNING] No Clover database found, skipping report generation
build	05-Mar-2015 20:44:56	[INFO] No report being generated for this module.
build	05-Mar-2015 20:44:56	[INFO] Using /default-clover-report descriptor.
build	05-Mar-2015 20:44:56	[INFO] Using Clover report descriptor: /tmp/mvn5516880637728429089resource
build	05-Mar-2015 20:44:56	[INFO] ------------------------------------------------------------------------
build	05-Mar-2015 20:44:56	[INFO] BUILD SUCCESS
build	05-Mar-2015 20:44:56	[INFO] ------------------------------------------------------------------------

 

The current situation is:

Bamboo ver 5.7.2 build 5716

  1. I installed Artifactory plugin, then the Maven Task 3.X task does not work, so I use Artifactory Maven 3 task instead.
  2. I want to disable IT tests in Clover, so I ran Clover with manual integration.
    I do not have Clover server, just using the Clover integrated in Bamboo.
  3. So I created a Stage containing one job for Clover.
  4. In the above job, I added tasks: 
    1. Source Code Checkout (default job)
    2. Script to save clover License to a file that will be used in step c.
    3. Artifactory Maven 3 task. See screenshot:
      (the build result is the same even if the root pom.xml was specified)
      Clover.PNG
  5. Other configuration:

    Clover1.PNGClover2.PNG
  6. Run the plan, and you will see the partial log on the top this post.

 

Can anybody tell me the solution or which step is incorrect?

Thank you in advance.

 

1 answer

0 vote

Bamboo Clover Plugin does not handle automatic Clover integration for the 'Artifactory Maven Task'. This will be fixed in Bamboo 5.9 (BAM-15711). In the meantime, you can configure manual integration.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,819 views 0 6
Read article

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