Clover Coverage Analysis sensor not firing on Groovy projects

prestontim · December 3, 2020, 7:55pm

SonarQube v8.5 (build 37579)
SonarQube Plugins: Groovy v1.6, Clover v4.1 (others can be seen in the screenshots below). (I have experimented with Groovy v1.7-SNAPSHOT, but it didn’t make a difference and caused problems so I had to roll it back).
SonarQube Gradle Plugin v2.6.1 (I have tried newer versions of this plugin, but it didn’t make any difference)

I have been unable to figure out why I cannot get the Clover coverage reports imported for Groovy projects on a SonarQube EE (8.5) instance. Coverage for these projects are imported properly on our SonarQube CE (6.7.7) instance.

I am setting the sonar.clover.reportPath property (see screenshot) and the file is present/valid on the build server. However, I am getting the following message when I run my (Gradle) SonarQube scan with debug-level logging:
‘Clover Coverage Analysis’ skipped because there is no related file in current project. I’ve tracked the message down to this line of code, but I don’t know enough about how the scanner executes to be sure why the sensor is being disqualified.

What am I missing?

Any assistance is appreciated.

ganncamp · December 3, 2020, 9:03pm

Hi,

Welcome to the community!

Sorry, but the Clover plugin isn’t supported here. Normally I would direct you to filing an issue on that project, but I’m not certain it’s actively maintained anymore.

Ann

prestontim · December 4, 2020, 12:53pm

Yeah, I realize that Clover isn’t supported, I’ve been through this with support.

I have filed an issue on their tracker. However, I’m not convinced that this is an issue with the Clover plugin since I am able to import coverage on Java projects. It seems more likely that this is an issue with either the Groovy plugin (also likely not supported) and/or the enterprise scanner itself.

So…let me ask this a different way. Generically-speaking, how can I figure out the criteria that is disqualifying a sensor (the line of code that I pointed to above)? Are there debug/trace-level logs that can give me more insight behind that message?

Colin · December 4, 2020, 1:14pm

Each plugin decides which language(s) it runs on.

github.com

sfeir-open-source/sonar-clover/blob/019fed1a719b5ab7788f4b0481edea17858d8734/src/main/java/org/sonar/plugins/clover/CloverSensor.java#L66


  return null;
}
private static boolean reportExists(@Nullable File report) {
  return report != null && report.isFile();
}
@Override
public void describe(SensorDescriptor descriptor) {
  descriptor.name("Clover Coverage Analysis");
  descriptor.onlyOnLanguages("java", "groovy");
}
@Override
public void execute(SensorContext context) {
  final File report = getReportFromProperty();
  if (reportExists(report)) {
    new CloverXmlReportParser(context, new InputFileProvider(fs)).collect(report);
  } else {
    Loggers.get(getClass()).warn(MISSING_FILE_MESSAGE);
  }

Looks like the plugin defines the wrong language key, groovy rather than grvy

github.com

Inform-Software/sonar-groovy/blob/a009f16f3ba89d41cdb727db8726587bd3691425/sonar-groovy-plugin/src/main/java/org/sonar/plugins/groovy/foundation/Groovy.java#L31


import java.util.ArrayList;
import java.util.List;
import org.apache.commons.lang.StringUtils;
import org.sonar.api.config.Settings;
import org.sonar.api.resources.AbstractLanguage;
import org.sonar.plugins.groovy.GroovyPlugin;
public class Groovy extends AbstractLanguage {
  public static final String KEY = "grvy";
  /**
   * Settings of the plugin.
   */
  private final Settings settings;
  /**
   * Default constructor
   */
  public Groovy(Settings settings) {

prestontim · December 4, 2020, 1:22pm

Colin…thank you so much!

I had noticed that while I was looking through all of the plugin code, but thought that might be a little too easy.

prestontim · December 4, 2020, 2:04pm

In case anybody else runs into this…

A PR has been submitted to sonar-clover: https://github.com/sfeir-open-source/sonar-clover/pull/45

system · December 11, 2020, 2:04pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.