I am evaluating Bamboo-Clover integration for distributed code coverage. I was successful in getting the aggregated code coverage in my integrated environment. However, the historical charts in Bamboo under Coverage Summary Section are not displayed.
I am running Bamboo 5.8.1 and clover version is 4.0.3.
Have used the following command to create the history point.
clean clover2:setup verify clover2:save-history clover2:clover
Please let me know if am missing any specific configuration required to display Historical charts (Total Coverage Percentage, Lines of Code, Non-Comment lines of code).
There are two kinds of historical charts:
Thanks for reply Marek. Here is the additional information.
Our build has a job with multiple tasks.
3. Install/Deploy the Addon on Remote Target Instance (JIRA/Confluence)
4. Run the Integration tests on the Remote Instance
Automatic Integration Case:
Our integration tests use the same clover.db (shared folder on network path) and we are able to get the coverage reports for complete distributed
coverage. But the historical reports are missing. We are able to view only Unit test reports on historical reports. We see that Clover runs
the save-history as part of maven package and since the integration tests are executed later they are not accounted in the historical reports.
Hence we guess we are missing the historical reports. Is that a correct assessment ?
Manual Integration Case:
If we do the manual integration in pom.xml and add the Clover goals in the tasks including the save-history, the history folder is generated
inside the build directories target folder which is different from the Automatic Integration where its generated parallel to target as .cloverhistory folder. We do not see the historical charts in Manual integration too. We are not sure if the charts on the plan summary page use a fixed location to get the reports. We tried configuring the location of XML report, but it did not help.
Can you please suggest the ideal way to get the historical charts data when using distributed coverage ?
It would be great if you could share details of your setup (such as screen shots of tasks configured, build log, pom file etc) - feel free to create a ticket at support.atlassian.com. Having information provided by you, I suppose that you shall use manual Clover integration, as your job has multiple tasks and integration tests are in a different task than compilation and packaging. You could try the following setup: 1. Checkout 2. Package - add Clover instrumentation here, e.g. "clover2:clover package" in case of Maven 3. Install/Deploy to remote machine - probably no changes are needed; optionally you may consider copying clover.db instead of keeping it on a shared network drive 4. Run integration tests - when do you compile code for integration tests? in this task or in task #2? 5. Generate Clover reports - e.g. "clover2:clover" in case of Maven; in case you have more than one clover.db you may also need to run "clover2:aggregate" or "clover2:merge" before; in case you want to have historical reports embedded in an HTML report you have to call "clover2:save-history" and use "maven.clover.generateHistorical=true" for "clover2:clover"; check location where HTML and XML reports are written and verify that folders specified in the "Clover XML report" field as well as in the "Clover Report (System)" artifact are correct.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
@Alice Camilla is a university student, currently writing her MA thesis in Archaeology. She's also a freelance blogger and content creator, writing about geeky stuff from productivity apps to JR...
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!
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