Manually triggered Github workflows on branches are pushed to main on sonarcloud.io

[pko]

Template for a good new topic, formatted with Markdown:

• ALM used: GitHub
• CI system used: GitHub
• Scanner command used: `./gradlew sonar --info
• Languages of the repository: Kotlin
• Error observed: When manually starting a workflow on a branch or tag, the results are publish on Sonarcloud.io as if run on the main branch. I expect this to be published as a branch run, shown in the Branches overview.
• Steps to reproduce: Manually trigger a Github workflow on a gradle project on a branch.
• Potential workaround: None known so far.

This seems to be the exact issue as described here: SonarCloud Github: always pushed to main branch on "workflow_dispatch"

[Colin]

Hey there!

We’ve seen this before. @sodul was kind enough to provide a workaround:

Sonarcloud-github-action publishes branch analysis to main and not the current branch

I was able to simplify the logic by doing just setting sonar.branch.name explicitly when not on a PR: sonar-project.properties: sonar.branch.name = ${env.SONAR_BRANCH} Then in a shell step of the workflow yaml: if [[ ! $GITHUB_BASE_REF ]]; then # GITHUB_BASE_REF is only set for PRs, we are on a branch. echo "SONAR_BRANCH=${GITHUB_REF_NAME}" >> $GITHUB_ENV fi This way the sonar.branch.name is the only parameter to set and only set if we are not on a pull r…

and I confirm there’s a ticket in our backlog to autoconfigure the branch when executed via workflow_dispatch

[heruan (Giovanni Lovato)]

Hi Colin, has this even been done? I’m having the same issue: running by workflow_dispatch on some branch but Sonar thinks it’s main.

[Colin]

Hey @heruan

Sorry to report the ticket is still open on our side. I can just point to the workaround shared by @sodul.

Sonarcloud-github-action publishes branch analysis to main and not the current branch

I was able to simplify the logic by doing just setting sonar.branch.name explicitly when not on a PR: sonar-project.properties: sonar.branch.name = ${env.SONAR_BRANCH} Then in a shell step of the workflow yaml: if [[ ! $GITHUB_BASE_REF ]]; then # GITHUB_BASE_REF is only set for PRs, we are on a branch. echo "SONAR_BRANCH=${GITHUB_REF_NAME}" >> $GITHUB_ENV fi This way the sonar.branch.name is the only parameter to set and only set if we are not on a pull r…

[heruan (Giovanni Lovato)]

Thank you for the quick feedback! I have tried the workaround, but I couldn’t make it work. I’m using the Gradle plugin and it does not read sonar-project.properties and does not seem to pick up the environment variable when configured in the task properties.

Do you think this is something that could be fixed in the short term? This behavior is messing up the history of the main branch analysis.