I have integrated clover manually in my project and under Build > Clover, it is showing properly.
Screenshot 2016-04-13 00.00.20.png
However when I try to view it in Bamboo's Reports Tab > Reports. Clover related stuff doesn't show anything.
Screenshot 2016-04-13 00.01.37.pngScreenshot 2016-04-13 00.01.43.png
Hi Ivan,
These Coverage, LOC and NCLOC charts aggregate data from build history. They're looking for metadata keys in build results named: CLOVER_BUILD_COVERAGE, CLOVER_LOC, CLOVER_NCLOC. The "-" character in the last screen shot attached suggests that is was unable to find any data. Please open build results from the specified date range (8-12 April) and check if these keys exist.
In case they're not present, please check build logs for presence of Clover-related warnings or errors.
Cheers
Marek
Hi @Marek Parfianowicz,
I can see the metadata keys in my build:
Screenshot 2016-04-13 09.14.00.png
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
And this one from a job metadata:
Screenshot 2016-04-13 09.18.35.png
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your metadata keys for a job and for a plan look correct. Could you please trigger data reindexing (https://confluence.atlassian.com/bamboo/reindexing-data-289277251.html) to check if this fixes the issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Marek Parfianowicz,
Is there a way to schedule indexing so we don't have to manually trigger it every time we want a report?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Why do you want to schedule the indexing? There's no need to do this (unless data is corrupted somehow). Did a problem with chart generation happen again? If yes, then feel free to create a ticket at support.atlassian.com.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The chart generation works after I did the indexing. However after a few days with several rebuilds, the chart is not updated. Its still showing from the previous dates. When I triggered again the indexing and generate the charts after, they were showing up to the latest. So I think I should always trigger indexing before I generate a chart which shouldnt be, right?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.