Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
04:34:29.860 INFO Load active rules
04:34:31.244 INFO Load active rules (done) | time=1386ms
04:34:31.426 ERROR You are running CI analysis while Automatic Analysis is enabled. Please consider disabling one or the other.
04:34:31.752 INFO EXECUTION FAILURE
Automatic Scan is turned off no initial scan completed. Deleted and re-added project to be sure.
Potential workaround: none scan check from github fails
I had another user just report that things started working after he flipped that toggle twice. So could you turn it on and back off. No you shouldn’t have to do that, but let’s see if it works. If it does, you’re unstuck! (and I’ll report this to the team.) If it doesn’t, I’ll flag this for the team to help.
What I’m seeing is that the scanner is still detecting Automatic Analysis as the analysis method, which is causing the process to fail because that feature is disabled:
ERROR Can not start analyzing because Automatic Analysis is disabled
Could you please try deactivating the CI autoconfiguration by setting the sonar.ci.autoconfig.disabled parameter to true in the scanner and let us know the result?
Normally, the autoconfig should detect that you are using GitHub Actions via the GITHUB_ACTION environment variable. Would you be able to verify if that variable holds a value when your workflow is running?