sonarqube-action broken

[stefan2904]

It looks like the kitabisa/sonarqube-action GH action is broken.

While the last build still worked, we now get:

Build container for action use: '/home/runner/work/_actions/kitabisa/sonarqube-action/master/Dockerfile'.
Error: Docker build failed with exit code 127

It looks like this is because the action uses npm to install some stuff, while the action's base image removed NPM 22 days ago ...

This can only be fixed at the action itself. There is already a "issue" at the action: kitabisa/sonarqube-action#33 (comment) but the action is unmaintained ...

---

Log

/usr/bin/docker build -t 6f1554:0a4c99409cb84fd1b450c404efc3e518 -f "/home/runner/work/_actions/kitabisa/sonarqube-action/master/Dockerfile" "/home/runner/work/_actions/kitabisa/sonarqube-action/master"
  Sending build context to Docker daemon  17.41kB
  
  Step 1/14 : FROM sonarsource/sonar-scanner-cli:4
  4: Pulling from sonarsource/sonar-scanner-cli
  8663204ce13b: Already exists
  65f45fbf9394: Pulling fs layer
  42ee3d49ed38: Pulling fs layer
  42ee3d49ed38: Verifying Checksum
  42ee3d49ed38: Download complete
  65f45fbf9394: Verifying Checksum
  65f45fbf9394: Download complete
  65f45fbf9394: Pull complete
  42ee3d49ed38: Pull complete
  Digest: sha256:b2277a01cc4cdcc4c867cf4663f40efac18241a8554518bdb530cf712c0df412
  Status: Downloaded newer image for sonarsource/sonar-scanner-cli:4
   ---> 3953ff8e072d
  Step 2/14 : LABEL "com.github.actions.name"="SonarQube Scan"
   ---> Running in 20da87cab00f
  Removing intermediate container 20da87cab00f
   ---> 4f0d4a87021d
  Step 3/14 : LABEL "com.github.actions.description"="Scan your code with SonarQube Scanner to detect bugs, vulnerabilities and code smells in more than 25 programming languages."
   ---> Running in 33504c62c413
  Removing intermediate container 33504c62c413
   ---> 61e7c1f3175e
  Step 4/14 : LABEL "com.github.actions.icon"="check"
   ---> Running in 661aee567b6d
  Removing intermediate container 661aee567b6d
   ---> 4848517dc198
  Step 5/14 : LABEL "com.github.actions.color"="green"
   ---> Running in 218092ab284f
  Removing intermediate container 218092ab284f
   ---> b1efd8472089
  Step 6/14 : LABEL version="0.0.2"
   ---> Running in 9bf9c7ac56e4
  Removing intermediate container 9bf9c7ac56e4
   ---> 79be5737c8b5
  Step 7/14 : LABEL repository="https://github.com/kitabisa/sonarqube-action"
   ---> Running in 2302110cf9f5
  Removing intermediate container 2302110cf9f5
   ---> 693ba42e1690
  Step 8/14 : LABEL homepage="https://kitabisa.github.io/"
   ---> Running in 5777c8932ec0
  Removing intermediate container 5777c8932ec0
   ---> 5e6b5598cd43
  Step 9/14 : LABEL maintainer="dwisiswant0"
   ---> Running in 30d68b0c86e4
  Removing intermediate container 30d68b0c86e4
   ---> 366989e0621e
  Step 10/14 : RUN npm config set unsafe-perm true &&   npm install --silent --save-dev -g [email protected] &&   npm config set unsafe-perm false &&   apk add --no-cache ca-certificates jq
   ---> Running in fcefa0ec64bb
  /bin/sh: npm: not found
  The command '/bin/sh -c npm config set unsafe-perm true &&   npm install --silent --save-dev -g [email protected] &&   npm config set unsafe-perm false &&   apk add --no-cache ca-certificates jq' returned a non-zero code: 127
  
  Warning: Docker build failed with exit code 127

Error: Docker build failed with exit code 127

[stefan2904]

@gdegani as long as this is broken (and the action is not fixed) we cannot send reports to sonar. This problem also exists for the backend repo.

I think this is currently not a big problem as there are no changed to the code quality metrics expected. But I think we need to keep an eye on that and make sure the reports are up to date when we put them in a deliverable.

[stefan2904]

I reported the issue upstream: kitabisa/sonarqube-action#34