Analysis on multi dependent repository project

SonarQube version:

Is there a good way to analyze a project that is based on multiple repositories. Each of the repositories has its own build, but that build depends on other repositories.

For example repository A fails to build because of a PR waiting to be merged on repository B. Since it is not possible to analyze the project without binaries, is there an option with sonar that would work around this problem (ex. while analyzing a PR on repository A to specify a PR on repository B which makes it buildable and use it).

The solution that does not involve Sonar is to create a pipeline which would handle the dependencies.


Welcome to the community!

I think you’re just going to have to run an analysis per repo. If you need to stitch them back together into a whole, Applications (aggregate projects) are available in Enterprise Edition($$) and above.