Broken Github Actions w/o showing an error

Template for a good new topic, formatted with Markdown:

  • ALM used (GitHub, Bitbucket Cloud, Azure DevOps)
  • CI system used (Bitbucket Cloud, Azure DevOps, Travis CI, Circle CI
  • Scanner command used when applicable (private details masked)
    /usr/bin/docker run --name d5332406ce45159b51b92e2375b4b7_666c24 --label 290506 --workdir /github/workspace --rm -e “GITHUB_TOKEN” -e “SONAR_TOKEN” -e “INPUT_ARGS” -e “INPUT_PROJECTBASEDIR” -e “HOME” -e “GITHUB_JOB” -e “GITHUB_REF” -e “GITHUB_SHA” -e “GITHUB_REPOSITORY” -e “GITHUB_REPOSITORY_OWNER” -e “GITHUB_RUN_ID” -e “GITHUB_RUN_NUMBER” -e “GITHUB_RETENTION_DAYS” -e “GITHUB_RUN_ATTEMPT” -e “GITHUB_ACTOR” -e “GITHUB_TRIGGERING_ACTOR” -e “GITHUB_WORKFLOW” -e “GITHUB_HEAD_REF” -e “GITHUB_BASE_REF” -e “GITHUB_EVENT_NAME” -e “GITHUB_SERVER_URL” -e “GITHUB_API_URL” -e “GITHUB_GRAPHQL_URL” -e “GITHUB_REF_NAME” -e “GITHUB_REF_PROTECTED” -e “GITHUB_REF_TYPE” -e “GITHUB_WORKSPACE” -e “GITHUB_ACTION” -e “GITHUB_EVENT_PATH” -e “GITHUB_ACTION_REPOSITORY” -e “GITHUB_ACTION_REF” -e “GITHUB_PATH” -e “GITHUB_ENV” -e “GITHUB_STEP_SUMMARY” -e “GITHUB_STATE” -e “GITHUB_OUTPUT” -e “RUNNER_OS” -e “RUNNER_ARCH” -e “RUNNER_NAME” -e “RUNNER_TOOL_CACHE” -e “RUNNER_TEMP” -e “RUNNER_WORKSPACE” -e “ACTIONS_RUNTIME_URL” -e “ACTIONS_RUNTIME_TOKEN” -e “ACTIONS_CACHE_URL” -e GITHUB_ACTIONS=true -e CI=true -v “/var/run/docker.sock”:“/var/run/docker.sock” -v “/home/runner/work/_temp/_github_home”:“/github/home” -v “/home/runner/work/_temp/_github_workflow”:“/github/workflow” -v “/home/runner/work/_temp/_runner_file_commands”:“/github/file_commands” -v “/home/runner/work/saschamannsde/saschamannsde”:“/github/workspace” 290506:74d5332406ce45159b51b92e2375b4b7 -Dsonar.projectKey=saigkill_saschamannsde -Dsonar.organization=saigkill
  • Languages of the repository
  • Only if the SonarCloud project is public, the URL
  • Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
    INFO: Scanner configuration file: /opt/sonar-scanner/conf/
    INFO: Project root configuration file: NONE
    INFO: SonarScanner
    INFO: Java 11.0.14 Alpine (64-bit)
    INFO: Linux 5.15.0-1024-azure amd64
    INFO: User cache: /opt/sonar-scanner/.sonar/cache
    INFO: Scanner configuration file: /opt/sonar-scanner/conf/
    INFO: Project root configuration file: NONE
    INFO: Analyzing on SonarCloud
    INFO: Default locale: “en_US”, source code encoding: “UTF-8” (analysis is platform dependent)
    INFO: Load global settings
    INFO: Load global settings (done) | time=570ms
    INFO: Server id: 1BD809FA-AWHW8ct9-T_TB3XqouNu
    INFO: User cache: /opt/sonar-scanner/.sonar/cache
    INFO: Load/download plugins
    INFO: Load plugins index
    INFO: Load plugins index (done) | time=564ms
    INFO: Load/download plugins (done) | time=3521ms
    INFO: Loaded core extensions: developer-scanner
    INFO: Found an active CI vendor: ‘Github Actions’
    INFO: Load project settings for component key: ‘saigkill_saschamannsde’
    INFO: Load project settings for component key: ‘saigkill_saschamannsde’ (done) | time=547ms
    INFO: ------------------------------------------------------------------------
    INFO: ------------------------------------------------------------------------
    INFO: Total time: 10.366s
    ERROR: Error during SonarScanner execution
    INFO: Final Memory: 7M/27M
    INFO: ------------------------------------------------------------------------
    ERROR: You are running CI analysis while Automatic Analysis is enabled. Please consider disabling one or the other.
    ERROR: Re-run SonarScanner using the -X switch to enable full debug logging.
  • Steps to reproduce
    Just run the workflow: saschamannsde/sonarcloud.yml at master · saigkill/saschamannsde · GitHub

Hey there.

It looks like Automatic Analysis is enabled, an therefore you can’t run CI-based analysis.

Can you check the project-level Administration > Analysis Method and turn off Automatic Analysis?


Ahh thank you- I didn’t realize I’d changed the project settings. Thank you!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.