[JENKINS-72915] Many identical Code Coverage Trends on UI using Jacoco Plugin for Multi-module Projects

Type: Bug
Resolution: Unresolved
Priority: Major
Component/s: jacoco-plugin
Labels:
None
Environment:
Jenkins Version 2.440.1
JaCoCo plugin 3.3.5

Similar Issues:
Powered by SuggestiMate

Show

CONTEXT:

We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use the next pipeline's stage for this purpose:

stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.value.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.value.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.value.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.value.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.value.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.value.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.value.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.value.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.value.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.value.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.value.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.value.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.value.maximumClassCoverage
                )
            }
        }
    }
}

Here: jacocoConfig.key - a name of a module, jacocoConfig.value - map of parameters for Jacoco

EXPECTED RESULT:{}

Correct logs for each module after each jacoco() execution. Code Coverage Trend on UI for each module.

ACTUAL RESULT:

The logs are correct. We see jacoco() execution for each project module. Different thresholds are applied for each module correctly. However, we see the same Code Coverage Trends on UI. And it looks like the Trend for the last scanned module (even not the trend for all lines in the project). We see around 40 covered and 15 missed lines here:

If we click on one of the trends, it always leads us to the same report about the whole project (jenkins_url/job_path/lastBuild/jacoco/). We see here around 550 covered lines and 100 missed in the whole project in total:

We also see redundant Coverage Trend's icons for all modules on the left:

I also reproduced it on local Jenkins easily. I installed only LTS Jenkins 2.440.1 and JaCoCo plugin 3.3.5 for it.

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

image-2024-03-24-19-53-58-981.png
73 kB
2024-03-24 18:54
image-2024-03-24-19-58-27-616.png
40 kB
2024-03-24 18:58
image-2024-03-24-19-59-41-422.png
54 kB
2024-03-24 18:59

Kirill Tikhonov created issue - 2024-03-24 18:07

Kirill Tikhonov made changes - 2024-03-24 18:08

Description

Original: We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

New: We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use next pipeline for this purpose:

{code]

Kirill Tikhonov made changes - 2024-03-24 18:08

Description

Kirill Tikhonov made changes - 2024-03-24 18:23

Description

New: We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use next pipeline's stage for this purpose:
{code:java}
stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacocoUtils.runJacoco(jacocoConfig.key, jacocoConfig.value)
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.maximumClassCoverage
                )
            }
        }
    }
}{code}

Kirill Tikhonov made changes - 2024-03-24 18:30

Description

Original: We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use next pipeline's stage for this purpose:
{code:java}
stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacocoUtils.runJacoco(jacocoConfig.key, jacocoConfig.value)
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.maximumClassCoverage
                )
            }
        }
    }
}{code}

New: *CONTEXT:*

We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use the next pipeline's stage for this purpose:
{code:java}
stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.value.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.value.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.value.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.value.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.value.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.value.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.value.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.value.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.value.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.value.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.value.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.value.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.value.maximumClassCoverage
                )
            }
        }
    }
}{code}
Here: jacocoConfig.key - a name of a module, jacocoConfig.value - map of parameters for Jacoco

{*}EXPECTED RESULT:{*}{*}{*}

Correct logs for each module after each jacoco() execution. Code Coverage Trend on UI for each module.

*ACTUAL RESULT:*

Logs are correct.

Kirill Tikhonov made changes - 2024-03-24 18:42

Description

Original: *CONTEXT:*

We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use the next pipeline's stage for this purpose:
{code:java}
stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.value.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.value.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.value.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.value.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.value.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.value.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.value.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.value.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.value.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.value.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.value.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.value.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.value.maximumClassCoverage
                )
            }
        }
    }
}{code}
Here: jacocoConfig.key - a name of a module, jacocoConfig.value - map of parameters for Jacoco

{*}EXPECTED RESULT:{*}{*}{*}

Correct logs for each module after each jacoco() execution. Code Coverage Trend on UI for each module.

*ACTUAL RESULT:*

Logs are correct.

New: *CONTEXT:*

We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use the next pipeline's stage for this purpose:
{code:java}
stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.value.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.value.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.value.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.value.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.value.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.value.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.value.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.value.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.value.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.value.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.value.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.value.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.value.maximumClassCoverage
                )
            }
        }
    }
}{code}
Here: jacocoConfig.key - a name of a module, jacocoConfig.value - map of parameters for Jacoco

{*}EXPECTED RESULT:{*}{*}{{*}}

Correct logs for each module after each jacoco() execution. Code Coverage Trend on UI for each module.

*ACTUAL RESULT:*

The logs are correct. We see jacoco() execution for each project module. However, we see the same Code Coverage Trends on UI. And it looks like the Trend for the last scanned module (even not the trend for all lines in the project):

If we click on one of the trends, it always leads us to the same report about the whole project:

We also see Coverage Report for all modules

Kirill Tikhonov made changes - 2024-03-24 18:45

Description

Original: *CONTEXT:*

We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use the next pipeline's stage for this purpose:
{code:java}
stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.value.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.value.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.value.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.value.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.value.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.value.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.value.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.value.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.value.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.value.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.value.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.value.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.value.maximumClassCoverage
                )
            }
        }
    }
}{code}
Here: jacocoConfig.key - a name of a module, jacocoConfig.value - map of parameters for Jacoco

{*}EXPECTED RESULT:{*}{*}{{*}}

Correct logs for each module after each jacoco() execution. Code Coverage Trend on UI for each module.

*ACTUAL RESULT:*

The logs are correct. We see jacoco() execution for each project module. However, we see the same Code Coverage Trends on UI. And it looks like the Trend for the last scanned module (even not the trend for all lines in the project):

If we click on one of the trends, it always leads us to the same report about the whole project:

We also see Coverage Report for all modules

New: *CONTEXT:*

We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use the next pipeline's stage for this purpose:
{code:java}
stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.value.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.value.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.value.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.value.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.value.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.value.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.value.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.value.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.value.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.value.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.value.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.value.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.value.maximumClassCoverage
                )
            }
        }
    }
}{code}
Here: jacocoConfig.key - a name of a module, jacocoConfig.value - map of parameters for Jacoco

{*}EXPECTED RESULT:{*}{*}{{*}}

Correct logs for each module after each jacoco() execution. Code Coverage Trend on UI for each module.

*ACTUAL RESULT:*

The logs are correct. We see jacoco() execution for each project module. However, we see the same Code Coverage Trends on UI. And it looks like the Trend for the last scanned module (even not the trend for all lines in the project):

If we click on one of the trends, it always leads us to the same report about the whole project:

We also see Coverage Report for all modules one the right:

Kirill Tikhonov made changes - 2024-03-24 18:47

Description

Original: *CONTEXT:*

We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use the next pipeline's stage for this purpose:
{code:java}
stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.value.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.value.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.value.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.value.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.value.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.value.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.value.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.value.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.value.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.value.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.value.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.value.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.value.maximumClassCoverage
                )
            }
        }
    }
}{code}
Here: jacocoConfig.key - a name of a module, jacocoConfig.value - map of parameters for Jacoco

{*}EXPECTED RESULT:{*}{*}{{*}}

Correct logs for each module after each jacoco() execution. Code Coverage Trend on UI for each module.

*ACTUAL RESULT:*

The logs are correct. We see jacoco() execution for each project module. However, we see the same Code Coverage Trends on UI. And it looks like the Trend for the last scanned module (even not the trend for all lines in the project):

If we click on one of the trends, it always leads us to the same report about the whole project:

We also see Coverage Report for all modules one the right:

New: *CONTEXT:*

We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use the next pipeline's stage for this purpose:
{code:java}
stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.value.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.value.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.value.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.value.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.value.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.value.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.value.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.value.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.value.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.value.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.value.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.value.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.value.maximumClassCoverage
                )
            }
        }
    }
}{code}
Here: jacocoConfig.key - a name of a module, jacocoConfig.value - map of parameters for Jacoco

{*}EXPECTED RESULT:{*}{*}{{*}}

Correct logs for each module after each jacoco() execution. Code Coverage Trend on UI for each module.

*ACTUAL RESULT:*

The logs are correct. We see jacoco() execution for each project module. However, we see the same Code Coverage Trends on UI. And it looks like the Trend for the last scanned module (even not the trend for all lines in the project):

If we click on one of the trends, it always leads us to the same report about the whole project:

We also see Coverage Report for all modules on the right:

I also reproduced it on local Jenkins easily installed LTS Jenkins and

Kirill Tikhonov made changes - 2024-03-24 18:48

Description

Original: *CONTEXT:*

We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use the next pipeline's stage for this purpose:
{code:java}
stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.value.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.value.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.value.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.value.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.value.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.value.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.value.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.value.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.value.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.value.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.value.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.value.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.value.maximumClassCoverage
                )
            }
        }
    }
}{code}
Here: jacocoConfig.key - a name of a module, jacocoConfig.value - map of parameters for Jacoco

{*}EXPECTED RESULT:{*}{*}{{*}}

Correct logs for each module after each jacoco() execution. Code Coverage Trend on UI for each module.

*ACTUAL RESULT:*

The logs are correct. We see jacoco() execution for each project module. However, we see the same Code Coverage Trends on UI. And it looks like the Trend for the last scanned module (even not the trend for all lines in the project):

If we click on one of the trends, it always leads us to the same report about the whole project:

We also see Coverage Report for all modules on the right:

I also reproduced it on local Jenkins easily installed LTS Jenkins and

New: *CONTEXT:*

We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use the next pipeline's stage for this purpose:
{code:java}
stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.value.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.value.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.value.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.value.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.value.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.value.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.value.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.value.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.value.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.value.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.value.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.value.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.value.maximumClassCoverage
                )
            }
        }
    }
}{code}
Here: jacocoConfig.key - a name of a module, jacocoConfig.value - map of parameters for Jacoco

{*}EXPECTED RESULT:{*}{*}{{*}}

Correct logs for each module after each jacoco() execution. Code Coverage Trend on UI for each module.

*ACTUAL RESULT:*

The logs are correct. We see jacoco() execution for each project module. However, we see the same Code Coverage Trends on UI. And it looks like the Trend for the last scanned module (even not the trend for all lines in the project):

If we click on one of the trends, it always leads us to the same report about the whole project:

We also see Coverage Report for all modules on the right:

I also reproduced it on local Jenkins easily installed LTS Jenkins 2.440.1 and Jacoco

Kirill Tikhonov made changes - 2024-03-24 18:50

Description

Original: *CONTEXT:*

We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use the next pipeline's stage for this purpose:
{code:java}
stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.value.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.value.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.value.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.value.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.value.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.value.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.value.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.value.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.value.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.value.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.value.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.value.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.value.maximumClassCoverage
                )
            }
        }
    }
}{code}
Here: jacocoConfig.key - a name of a module, jacocoConfig.value - map of parameters for Jacoco

{*}EXPECTED RESULT:{*}{*}{{*}}

Correct logs for each module after each jacoco() execution. Code Coverage Trend on UI for each module.

*ACTUAL RESULT:*

The logs are correct. We see jacoco() execution for each project module. However, we see the same Code Coverage Trends on UI. And it looks like the Trend for the last scanned module (even not the trend for all lines in the project):

If we click on one of the trends, it always leads us to the same report about the whole project:

We also see Coverage Report for all modules on the right:

I also reproduced it on local Jenkins easily installed LTS Jenkins 2.440.1 and Jacoco

New: *CONTEXT:*

We have multi-module projects and need to create reports for each module and also be able to assign different thresholds for different modules.

We use the next pipeline's stage for this purpose:
{code:java}
stage('Jacoco Code Coverage') {
    steps {
        script {
            jacocoConfigs.each {jacocoConfig ->
                jacoco(
                    execPattern: jacocoConfig.key + '/build/jacoco/*.exec',
                    classPattern: jacocoConfig.key + '/build/classes/java/main',
                    sourcePattern: jacocoConfig.key + '/src/main/java',
                    exclusionPattern: jacocoConfig.value.exclusionPattern,
                    changeBuildStatus: true,
                    runAlways: true,
                    minimumInstructionCoverage: jacocoConfig.value.minimumInstructionCoverage,
                    maximumInstructionCoverage: jacocoConfig.value.maximumInstructionCoverage,
                    minimumBranchCoverage: jacocoConfig.value.minimumBranchCoverage,
                    maximumBranchCoverage: jacocoConfig.value.maximumBranchCoverage,
                    minimumComplexityCoverage: jacocoConfig.value.minimumComplexityCoverage,
                    maximumComplexityCoverage: jacocoConfig.value.maximumComplexityCoverage,
                    minimumLineCoverage: jacocoConfig.value.minimumLineCoverage,
                    maximumLineCoverage: jacocoConfig.value.maximumLineCoverage,
                    minimumMethodCoverage: jacocoConfig.value.minimumMethodCoverage,
                    maximumMethodCoverage: jacocoConfig.value.maximumMethodCoverage,
                    minimumClassCoverage: jacocoConfig.value.minimumClassCoverage,
                    maximumClassCoverage: jacocoConfig.value.maximumClassCoverage
                )
            }
        }
    }
}{code}
Here: jacocoConfig.key - a name of a module, jacocoConfig.value - map of parameters for Jacoco

{*}EXPECTED RESULT:{*}{*}{{*}}

Correct logs for each module after each jacoco() execution. Code Coverage Trend on UI for each module.

*ACTUAL RESULT:*

The logs are correct. We see jacoco() execution for each project module. However, we see the same Code Coverage Trends on UI. And it looks like the Trend for the last scanned module (even not the trend for all lines in the project):

If we click on one of the trends, it always leads us to the same report about the whole project:

We also see Coverage Report for all modules on the right:

I also reproduced it on local Jenkins easily. I installed only LTS Jenkins 2.440.1 and JaCoCo plugin 3.3.5 for it.

Kirill Tikhonov made changes - 2024-03-24 18:52

Attachment

New: screenshot-1.png [ 62353 ]

Assignee:: Ognjen Bubalo

Reporter:: Kirill Tikhonov

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2024-03-24 18:07

Updated:: 2024-03-25 13:09

Jenkins

Details

Description

Attachments

Attachments

Activity

People

Dates