1 answer

1 accepted

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.

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.