Pipeline Build Repo
Pipeline Build SonarScan
Pipeline Deploy Repo
Pipeline Deploy SonarGate
But without the host.url said the same message “ERROR: SONARQUBE SERVER [HTTP://LOCALHOST:9000] CAN NOT BE REACHED”
What am I doing wrong?
@Colin there is not sonar-project.propeties file created, or do we need to manually create it ? i was guessing that by using sonar cloud it’s going to auto bind
Typically, in Bitbucket Pipelines, the default host should be https://sonarcloud.io unless overriden somewhere. This relies on the presence of the BITBUCKET_BUILD_NUMBER environment variable. Is that environment variable available during your build?
In any case, even if you still need to manually set sonar.host.url, it’s not the end of the world. I would encourage leaving out -Dsonar.login and relying on having SONAR_TOKEN configured)
You may want to try using the latest version of the pipe, 1.4.0.
Can you confirm how/where you’re setting SONAR_TOKEN? A screenshot would be helpful.
Amazing!
Currently is scanning!
But now get stuck in…
ERROR: eslint-bridge Node.js process is unresponsive. This is most likely caused by process running out of memory. Consider setting sonar.javascript.node.maxspace to higher value (e.g. 4096).
Current yaml definition that’s “out of memory”. 13:06:42.741 ERROR: eslint-bridge Node.js process is unresponsive. This is most likely caused by process running out of memory. Consider setting sonar.javascript.node.maxspace to higher value (e.g. 4096).
definitions:
caches:
sonar: ~/.sonar/cache # Caching SonarCloud artifacts will speed up your build
services:
docker:
memory: 1024 #increasing docker service memory
steps:
- step: &build-test-sonarcloud
name: Build, test and analyze on SonarCloud
size: 2x
caches:
- sonar
script:
- pipe: sonarsource/sonarcloud-scan:1.4.0
variables:
DEBUG: "true"
EXTRA_ARGS: '-Dsonar.host.url=https://sonarcloud.io'
- step: &check-quality-gate-sonarcloud
name: Check the Quality Gate on SonarCloud
script:
- pipe: sonarsource/sonarcloud-quality-gate:0.1.4