SEI uses Rest APIs to connect to Sonarqube. Using these API calls SEI ingests
metadata for Sonar issues, analyses, projects, and quality gates. This metadata is
used to generate engineering metrics and insights.
The full details of all the fields are
mentioned below.
Sonar analyses
| Metadata |
|---|
- key
- data
- projectVersion
- buildString
- manualNewCodePeriodBaseline
- revision
- events
|
Sonar branches
| Metadata |
|---|
- name
- isMain
- type
- analysisDate
- excludedFromPurge
- status
- qualityGateStatus
- bugs
- vulnerabilities
- codeSmells
- measures
- metric
- value
- data_type
- bestValue
|
Sonar pull request and issues
| Metadata |
|---|
- key
- title
- branch
- base
- status
- qualityGateStatus
- bugs
- vulnerabilities
- codeSmells
- analysisDate
- url
- target
- measures
- metric
- value
- data_type
- bestValue
- issues
- key
- rule
- severity
- component
- pullRequest
- line
- textRange
- flows
- status
- message
- effort
- debt
- author
- tags
- comments
- creationDate
- updateDate
- type
- organization
- components
- transitions
- rules
- users
- actions
- analyses
|
Sonar projects
| Metadata |
|---|
- organization
- key
- name
- qualifier
- visibility
- lastAnalysisDate
- revision
- uuid
- path
- longName
- enabled
- measures
- metric
- value
- data_type
- bestValue
- branches
- pullRequests
- analyses
|
Sonar quality gates
| Metadata |
|---|
- id
- name
- isDefault
- isBuiltIn
- actions
- rename
- setAsDefault
- copy
- associateProjectsdelete
- manageConditions
- create
- status
- statusFailing
- failing
|