We are facing the above error (Mentioned in the title) while running the bitbucket yml file. We have tried substituting the value by taking https://community.atlassian.com/t5/Bitbucket-questions/Pipelines-Exceeded-Memory-Limit-Container-exceeded-memory-limit/qaq-p/1040776 as reference but still landed up with the same error.
Can someone mentioned what needs to be updated here?
- step: &sonarcloud
name: Analyze on SonarCloud
- pipe: sonarsource/sonarcloud-scan:0.1.5
- step: *sonarcloud
Try to use newer version of the pipe, the one that you are using (0.1.5) is really old.
The current version is 1.0.1.
If that doesn't work, you will need to experiment with the docker memory settings and/or with the node size.
Try overriding the size for the single step that is failing:
- step: size: 2x # Double resources available for this step.
definitions: services: docker: memory: 2048
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events