Page History
...
Finally, Maven and SonarQube need to be configured with the correct properties to be able to read your Blueriq Model of interest. Maven takes care of this by reading a pom file containing the following properties:.xml file.
Below, you can see
- An explanation of the properties in the pom
- An example of a pom
- The location where to save the pom
| Property | Required | Default | Description |
|---|---|---|---|
sonar.blueriq.managementservice | Required for managementservice | Url to the management service, if this property is set then all other managementservice properties must also be set. If this is not set, then the branchexportlocation must be set. | |
sonar.blueriq.repository | Required for managementservice | Name of the repository. | |
sonar.blueriq.branch | Required for managementservice | Name of the branch. | |
sonar.blueriq.username | Required for managementservice | Studio username credential. | |
sonar.blueriq.password | Required for managementservice | Studio password credential. | |
| sonar.blueriq.authentication | Required for managementservice | Studio authentication mode, currently only BASIC is supported | |
| sonar.blueriq.branchexportlocation | Required for export file | Location of a branch export zip from the studio, if this is set then the managementservice property must not be set. | |
sonar.blueriq.projects | Required | A comma separated list of blueriq project names. | |
| sonar.blueriq.workingDir | Required | Relative path inside the executing directory where the BMA plugin creates files to index issues and measures. | |
| sonar.blueriq.skipanalysis | Optional | false | Set to true if the BMA plugin shouldn't be triggered for the current project. This is useful when scanning projects without Blueriq, or when no connection can be made to the management service. |
...
Overview
Content Tools