nebula-plugins / nebula-plugins/nebula-project-plugin

Jacoco's execution data not registered with Gradle 6?

Open
#62 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Groovy
Stars
98
Forks
19
PR merge metrics
No merged PRs in 30d

Description

Hi everyone!

First of all: Thanks for your great plugin! We use it in most of our projects! 👍

I updated the plugin's version in one of our projects from 3.4.0 to 7.0.8 and our Sonar integration stopped working. Sonar/Jacoco could not find the integrationTest task's execution data anymore.

I had to add the following line to Jacoco's configuration in my build.gradle:

jacocoTestReport {
    executionData(integrationTest) // <-- here
    reports {
        xml.enabled true
    }
}

The project uses Gradle 6.1.

Might this be a bug or am I missing something?

Thanks,

Christopher

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the Sonar/Jacoco integration with Gradle 6.1 using the plugin versions described, starting from the build.gradle jacocoTestReport configuration and the integrationTest task. Compare execution-data behavior between versions 3.4.0 and 7.0.8; done means integrationTest execution data is found without manually adding executionData(integrationTest).

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.