Getting coverage analysis without any settings

We use SonarCloud - Github with Github Actions.
Our repository is a monorepo : PHP , Laravel , JS .

We have two branches:

  • release
  • production

We disabled automatic analysis and started to use GitHub Action to be able to have another Long-lived branch which is production in our case.

Firstly, we pushed the build.yml file including test coverage steps to .github/workflows/build.yml. It worked but then we removed the test coverage steps and updated the file again as below.

Now, we don’t understand the three points below:

  1. Why do we still have code coverage analysis?
  2. Why do we not have sonarcloud analysis for production branch? Do we need to have at least a PR from the production branch?
  3. SonarCloud started to miss some PRs. It began after we disabled automatic analysis and started to use GitHub Action.
name: build SC

      - release        # The default branch
      - production-*    # The other branches to be analyzed

      - release        # The default branch
      - production-*
    types: [opened, synchronize, reopened]

    name: SonarCloud
    runs-on: ubuntu-latest
      - uses: actions/checkout@v2
          fetch-depth: 0  # Shallow clones should be disabled for a better relevancy of analysis
      - name: SonarCloud Scan
        uses: SonarSource/sonarcloud-github-action@master
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}  # Needed to get PR information, if any
          SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}

A screenshot from a PR:

1 Like

Hey there,

SonarCloud assumes that if you’re using CI-Based Analysis, you want to provide coverage information. You can turn this off by excluding all files from coverage.

Probably your GitHub Action isn’t running on the production branch or branches targeting it. Looking at the GitHub Actions YAML file, it wouldn’t trigger on a branch named production, only production-something.

Hello @Colin ,

Thank you for your help.

The first issue below is resolved. :clap:
For the third issue, I need to gather more information, so I keep working on it.

For the second issue, after I made your suggestion and push the files to production branch as well, I get production branch on SonarCloud. However, it is listed under short-lived branches. How can I make it long-lived branch?

You’ll need to delete the branch and adjust the long-lived branches pattern before triggering a new analysis of the production branch… A project-administrator can take all of these actions from the project-level Branches page.

Hello @Colin,

Thanks for the prompt reply.

So, I should follow the steps below, respectively:

  1. Delete the branch
  2. Adjust the long-lived branches pattern
    My other long-lived branch is production. So the pattern should be (branch|release) instead of (branch|release)-.*.
  3. Trigger a new analysis of the production branch

Can you please confirm?

Your pattern will have to match the word production exactly – so perhaps production|((branch|release)-.*) or just (production|release) if those are the only two branch names you expect.

Hello @Colin,

I tried what you said. I have release branch and production branch. I don’t expect any other long-lived branches for now.

However, I cannot get the production branch whereas I get the analysis for the PR of production:


@Colin Hang on. It worked right now.

Thanks for your support. :clap: :slightly_smiling_face:

1 Like