如何让SonarCloud读取Travis CI生成的lcov覆盖率文件？

Hey there, let's work through this SonarCloud coverage issue together. I’ve tackled similar setup problems with React apps, Travis, and SonarCloud before, so here are the key checks and fixes to try:

1. Confirm the LCOV File Path in Your Configuration #

First, make sure SonarCloud knows exactly where your lcov.info file lives. Create React App generates coverage reports in coverage/lcov.info by default when you run npm test -- --coverage.

• If you use a sonar-project.properties file, verify this line exists and points to the correct path:

  sonar.javascript.lcov.reportPaths=coverage/lcov.info
  

• If you’re passing the path directly in your Travis config, ensure the SonarCloud scanner command includes this parameter:

  sonar-scanner -Dsonar.javascript.lcov.reportPaths=coverage/lcov.info
  

2. Ensure Coverage Runs Before SonarCloud in Travis #

The order of commands in your .travis.yml is critical. You need to generate the coverage report first, then run the SonarCloud scan. Your script section should look like this:

script:
  - npm test -- --coverage
  - sonar-scanner

Also, double-check that no cleanup steps (like npm run clean) are deleting the coverage folder before SonarCloud runs.

3. Dig Into Travis Build Logs for Clues #

Head to your Travis build logs and look for two key details:

• Confirm the npm test -- --coverage command actually outputs the lcov.info file. You should see a line like Writing coverage report to coverage/lcov.info.
• Check the SonarCloud scanner logs for warnings like No coverage information will be saved because LCOV file cannot be found – this will tell you if SonarCloud is looking in the wrong spot or if the file doesn’t exist.

4. Verify the LCOV File Exists in Travis #

Add a quick debug step to your .travis.yml to confirm the file is present before SonarCloud runs:

script:
  - npm test -- --coverage
  - ls -la coverage/  # Lists all files in the coverage directory
  - sonar-scanner

This will show you if lcov.info exists and has the correct permissions.

5. Check SonarCloud Project UI Settings #

Sometimes the SonarCloud UI settings override your config files. Log into your SonarCloud project, go to Project Settings > General Settings > Languages > JavaScript/TypeScript, and make sure the LCOV Report Path matches the path where your file is generated.

If you’re still stuck after trying these steps, share the relevant sections of your .travis.yml and sonar-project.properties files, plus any error messages from the Travis logs – that will help narrow down the issue further!

内容的提问来源于stack exchange，提问作者ThomasNichols89