Mono Repo / Step Stops abruptly in Bitbucket pipelines

[sonar2 (Dnellutla)]

We are doing Quality Gate Analysis of a Mono Repo in bitbucket pipelines , the sonar quality gate steps runs parallely for the different projects based on changeSets in the PR.

The Analysis is run on a Runner.

Some of the steps stop abruptly stating pipeline failure. There is no error stacktrace that is printed on the terminal.
What is the reason for that stop, would it be possible to throw some light on this issue.

[Colin]

It sounds like it could be an issue with how much memory is allocated to your Bitbucket Pipelines (and the underlying services). Take a look at this answer here:

Analyze an angular project on Bitbucket pipeline using sonar-cloud-scan pipe failed

We were able to solve this issue by allowing more memory for docker service. By default docker service is running with 1024 MO so we increase that memory to 2048. https://confluence.atlassian.com/bitbucket/use-services-and-databases-in-bitbucket-pipelines-874786688.html Now our pipeline.yml looks like this: image: node:10 clone: depth: full # SonarCloud scanner needs the full history to assign issues properly definitions: caches: sonar: ~/.sonar/cache # Caching SonarCloud artifacts …