Mono Repo / Step Stops abruptly in Bitbucket pipelines

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.

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:

1 Like