Installation with Gitlab (cannot trigger sonar scanner cli, pipeline on "stuck" status)

Hello,

This is our first installation of SonarQube and we cannot trigger the sonar scanner cli from a gitlab instance : the pipeline stay on “stuck” status at the first step (sonar is never joined).

Informations :

Our conf gitlab-ci is : 
sonarqube-check:
  stage: test
  image: 
    name: sonarsource/sonar-scanner-cli:latest
    entrypoint: [""]
  variables:
    SONAR_USER_HOME: "${CI_PROJECT_DIR}/.sonar"
    GIT_DEPTH: "0"
  cache:
    key: "${CI_JOB_NAME}"
    paths:
      - .sonar/cache
  script: 
    - sonar-scanner
  allow_failure: true
  only:
    - merge_requests
    - master
    - develop

We have followed the doc but some points are not very clear for us :

  • Do we really need to install a gitlab-runner ? (we do, but in which mode ? ssh ? shell ?)
  • Should we have an httpS link between the two vm ? (seems not according to the doc)
  • How could we debug this problem ? (we don’t have access ssh access to our gitlab instance

We need to kwow what action we could do to investigate in our problem.

Thanks in advance

Solved, problem with Gitlab Runner (add sudo on declaration and add tag on the runner).

1 Like

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