[FOLIO-3101] 0% coverage reported by Sonarcloud for mod-data-export Created: 31/Mar/21  Updated: 01/Apr/21  Resolved: 31/Mar/21

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P3
Reporter: John Malconian Assignee: John Malconian
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by MDEXP-388 0% coverage reported by Sonarcloud fo... Closed
Sprint: DevOps Sprint 111
Development Team: FOLIO DevOps

 Description   

Sonarcloud reports 0% code coverage for master branch builds of mod-data-export. Coverage report not found/imported into Sonarcloud.



 Comments   
Comment by John Malconian [ 31/Mar/21 ]

From Jenkins build log:

[WARNING] No coverage report can be found with sonar.coverage.jacoco.xmlReportPaths='target/site/jacoco/jacoco.xml'. Using default locations: target/site/jacoco/jacoco.xml,target/site/jacoco-it/jacoco.xml,build/reports/jacoco/test/jacocoTestReport.xml
Comment by John Malconian [ 31/Mar/21 ]

The lack of coverage report is due to the following commit.

https://github.com/folio-org/mod-data-export/commit/df6cf38eaed19955bde77a78941f8e0db790be96#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R494

Remove '<argLine>-Dfile.encoding=UTF-8</argLine>' from the POM and the issue should be resolved.

Generated at Thu Feb 08 23:25:37 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.