I have configured a plan which has one job and that job contains two tasks. The first task is to checkout the latest source code and the second task runs clover with the settings clover2:setup test clover2:aggregate clover2:clover. When I run this plan the build completes successfully and I am able to view the clover tab on the main plan summary page and the job summary pages but I cannot view this tab on the build summary pages ( when you select a number from the plan summary page to go to a particular build summary ).
I am wondering if this is because there is something wrong with my settings that could cause this. I am not using "automatically integrate Clover into this build" and I am instead using the "Clover is already integrated in this build..." option and have provided the correct location for the clover.xml file which it is able to locate.
I also have the clover plugin configured as follows in my parent pom.xml within plugin management.
<plugin> <groupId>com.atlassian.maven.plugins</groupId> <artifactId>maven-clover2-plugin</artifactId> <version>3.1.8</version> </plugin>
Please let me know if there is something I am possibly missing in my configurations.
The Clover HTML report is associated with a Job Summary page and not with a Build Summary page because a single build may contain multiple jobs, each of them having it's own Clover report.
The Plan Summary page also contains Clover tab, because it has just a metrics summary from all Clover-enabled jobs.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
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