Hi @Hamid
If you had a build that was successful previously, and this has suddenly failed - I would suggest checking the build logs for both successful and failed builds to see if there is a difference in the image SHA shown in the Build Setup of your build logs. If there is a change, I'd suggest copy-pasting the image SHA for a successful build into your YML configuration where the build image is defined and attempting to run a fresh build to see if the image is the problem:
Example
// Build logs
Images used:
build : docker.io/atlassian/default-image@sha256:a7cbf7b491d60202dcdec4628679b8ba6da27b8fffa8bce2cc3d29a9ac9359f3
// YML config:
image: docker.io/atlassian/default-image@sha256:a7cbf7b491d60202dcdec4628679b8ba6da27b8fffa8bce2cc3d29a9ac9359f3
If this is not the case - I'd suggest enabling debugging as mentioned in the error and reaching out to the SonarSource community, as the error shown is not Pipelines-specific:
You can also raise a ticket with our support team directly, as you are entitled to Standard level support due to your workspace membership of a Standard subscription workspace - please use the paid workspace URL when prompted:
Cheers!
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.