# Can't get scoverage report to import

**URL:** <https://community.sonarsource.com/t/cant-get-scoverage-report-to-import/57627>\
**Category:** SonarQube Cloud\
**Created:** [February 3, 2022, 10:09pm UTC](https://community.sonarsource.com/t/cant-get-scoverage-report-to-import/57627 "2022-02-03T22:09:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pgruetter](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/pgruetter/32/29976_2.png) [@pgruetter](https://community.sonarsource.com/u/pgruetter)\
**Post date:** [February 3, 2022, 10:09pm UTC](https://community.sonarsource.com/t/cant-get-scoverage-report-to-import/57627/1 "2022-02-03T22:09:19Z")

</div>

Hi all

We’re using sonarcloud on an open source project.  
I’m trying to setup scoverage but can’t get sonarcloud to import the report.

We’re using GitHub actions to execute the build. Result is here:

> **[Include scoverage report · smart-data-lake/smart-data-lake@544fa48](https://github.com/smart-data-lake/smart-data-lake/runs/5058498015?check_suite_focus=true)**
>
> Framework to quickly build and maintain Smart Data Lakes - Include scoverage report · smart-data-lake/smart-data-lake@544fa48

In step “Build with Maven for Scala 2.12” you can see that it successfully generated the scoverage report:  
`[INFO] Written XML coverage report [/home/runner/work/smart-data-lake/smart-data-lake/target/scoverage.xml]`

In sonarcloud under Administration → Languages → Scala → Path to Scoverage report, I’m trying to set the correct path.  
So far I’ve tried:

- \*\*/target/scoverage.xml
- target/scoverage.xml
- \*\*\target\scoverage.xml
- target\scoverage.xml
- /home/runner/work/smart-data-lake/smart-data-lake/target/scoverage.xml

But for all of these, I receive a warning  
`Unable to import 1 Scoverage report file(s). Please check that property 'sonar.scala.coverage.reportPaths' is correctly configured and the analysis logs for more details.`

What’s the correct path to put here?

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [February 4, 2022, 9:58am UTC](https://community.sonarsource.com/t/cant-get-scoverage-report-to-import/57627/2 "2022-02-04T09:58:36Z")

</div>

Hey there.

No matter what configuration you do, coverage information is not available when using [Automatic Analysis](https://docs.sonarcloud.io/advanced-setup/automatic-analysis) – you would have to switch to CI-based analysis to import your coverage reports.

I still find it really insightful how you **expected** it to work – so I’ll pass that along. 🙂 We would eventually like to have coverage information available in automatic analysis scenarios.

---

<div class="post-metadata">

**Author:** ![pgruetter](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/pgruetter/32/29976_2.png) [@pgruetter](https://community.sonarsource.com/u/pgruetter)\
**Post date:** [February 4, 2022, 12:56pm UTC](https://community.sonarsource.com/t/cant-get-scoverage-report-to-import/57627/4 "2022-02-04T12:56:24Z")

</div>

Ah, that explains it of course! Didn’t see that, thanks for the information.  
I’ll have to see how much work it is to switch to GitHub actions. 👍