...

SonarQube uses indexed folders and files of a project to assign issues and measures on. With a Java or C# project the source directory is scanned and indexed into SonarQube. After the files have been indexed an analyzer is run to scan the files for issues and collects its measures. Since Blueriq doesn't work with a source directory but with a branch export from the Management Service, we need to create our own folder structure. Therefore a property needs to be set sonar.blueriq.workingDir, where the BMA can create a folder structure that represents a blueriq project structure. This includes the repository and branch.

Scope of analysis 

The Model Analyzes can only analyze the content of project which are created in the project itself. For more information see Analysis Scope.

Running analysis

To the perform an analysis the command “mvn sonar:sonar” must be executed from a command prompt, in the directory where the pom.xml is located. When this command is executed, it will fetch a branch export from the management service and run analysis on it. When the analysis is done the command prompt will inform that the analysis was successful.

...

After clicking on the project, a new screen will appear with three tabs to browse through the analysis results:

• Issues
• Measures
• Code

Scope of analysis 

...

Code 

The third tab in the upper left corner, called Code, gives you an overview of your projects. When clicking on "Open Component's Page" button in front a project (highlighted in red in the image), the focus will move to that project and its homepage with be displayed, showing only its measures. The breadcrumbs trail at the top of the page will also be updated.

...

You can view the issues of your Blueriq Model by clicking the Issues tab in the upper left corner of your screen:

Also see:

Rule Parameters