The Pipeline you shared shows sonarsource/sonarcloud-quality-gate:0.1.6, but the screenshot of logs you shared shows sonarsource/sonarcloud-quality-gate:0.14. Are you sure you’re looking at the right pipeline/logs?
- step: &build-test-sonarcloud
name: Build, test and analyze on SonarCloud
caches:
- node # See https://confluence.atlassian.com/bitbucket/caching-dependencies-895552876.html
- sonar
script: # Build your project and run
- pipe: sonarsource/sonarcloud-scan:2.0.0
variables:
EXTRA_ARGS: "--exclude=src/@fuse/* -X"
- step: &check-quality-gate-sonarcloud
name: Check the Quality Gate on SonarCloud
script:
- pipe: sonarsource/sonarcloud-quality-gate:0.1.6
variables:
EXTRA_ARGS: "--exclude=src/@fuse/*"
In any case, I think what will be truly interesting is the log output from sonarsource/sonarcloud-scan of the same pipeline where sonarsource/sonarcloud-quality-gate fails to locate an analysis, if you can share that.
Currently i attached perfect files, I am sure about this
Can you tell at where can change in bitbucket-pipeline.yml file then the result should get different. then you can understand what and where actual issue is happen.
“errorMessage”: “Impossible to process any new analysis. The plan for the organization ‘*******technology’ has expired. \nPlease contact the administrator of the organization to resolve this issue.”,
show above message
So our plan is expired then we not able to run the sonarsource/sonarcloud-quality-gate right ?