Using BitBucket Pipelines as the CI tool, code stored on BitBucket.
PR Summary marked as passed but still get this The last analysis has failed error which also shows up in BitBucket PR, thus blocking the PR from being merged.
Triggering the pipeline that does the scanning again, will probably resolve the issue, but it’s not a guarantee.
Hi,
Welcome to the community and thanks for this report!
Looks like you hit a race condition. This analysis failed with an “analysis too old” error. That means you had two analyses going at the same time and the newer one finished first. You can happily ignore this and proceed.
HTH,
Ann
Yes, this scan ran on a monorepo, that contains multiple services. The scan is run in parallel steps on each service (as is the build, and the report seems to be on a PR. What do you recommend as a solution for this scenario?
Hi,
You’re going to have to configure CI-based analysis. Automatic analysis simply doesn’t support monorepos.
HTH,
Ann
I don’t think that is an option since all services are Java/Maven based, and CI-based analysis is not supported for this. Currently this is how i’m triggering the scanning for each service: SonarScanner for Maven | SonarQube Cloud | Sonar Documentation.
any recommendations?
Hi,
Huh? CI-based analysis is absolutely supported for Java/Maven.
Ann
first info block on the page says these pipes are not available for java/maven.
Hi,
Fair enough. I’ll ping the docs folks about that. And the very first section has a Maven example.
Ann
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.