SonarQube is an open source platform for continuously monitoring code quality. It detects bugs, vulnerabilities, and code smells based on configured quality rules and profiles. Projects can define quality gates that check thresholds for metrics like issues, coverage, and duplications to flag the quality status as passed, warning, or failed. SonarQube allows comparing metrics across versions to track quality over time and supports code processes like nightly and pull request analysis. A community provides support through rule and profile updates, new plugins, and biweekly meetings to discuss quality concerns.

1. Track code quality
with SonarQube

2. HELLO!
I am Dmytro Patserkovskyi
Project Manager and founder
of Dev SonarQube Community at V.I.Tech
email: dmytro.wng@gmail.com

3. SOURCE CODE SHOULD BE
Simple
& Readable
Extendable
Testable
& Covered with Tests
Flexible

4. But is it really is?
What technical debt
on your project?

5. An open source platform for continuous
inspection of code quality

6. Quality Rules and Profiles
Code Smells Bugs Vulnerabilities
Quality Profile

7. Rules Plugins and Repositories
44
53
357
43
73

8. Quality Gates
Set of boolean conditions per project,
based on measure thresholds.
Passed
Warning
Failed

9. Quality Gates
Metric Operator
Open Issues Is greater than 70 100
Blocker Issues Is greater than 0
Dublications Is greater than 0.5 1
New Issues Is greater than 0 10
Overall Coverage Is less than 85 80
Unit Test Failures Is greater than 0

10. Quality of New Code
Comparison measures for different versions
Good for long term projects
Tracking quality of code, added in current snapshot

11. Code Processes
Master branch
Nightly
PullRequest Each update

12. Support Team for SonarQube

13. Administrator
Sonar support and monitoring
Sonar upgrade (new minor version every 2 months)
Plugins upgrade (new minor version every month)

14. Dev Sonar Community
Working on Rules List
Updating Quality Profiles
Looking for new Plugins

15. Project Teams
Update project analysis frequently
Monitoring Quality of own project
Defining project Quality Gate
Voice and discuss all concerns with Sonar Community

16. Support Processes
Modifications
Monthly
Meetings
Biweekly
Feedbacks
On-demand
Discussions
On-demand
Upgrade
Monthly

17. 24/7 monitoring and transparency

18. Summary
◉ Start from small: perform analysis
◉ Track code quality everyday
◉ Develop your own standard, or use existing
◉ Organize support process to make SonarQube alive
◉ Transparency 24/7, even for customers

19. THANKS!
Resources
◉ http://sonarqube.org
◉ http://docs.sonarqube.org/display/PLUG/Plugin+Library
◉ https://analysis.apache.org/
Links
◉ https://facebook.com/dmytro.wng
◉ http://slideshare.net/DmytroPatserkovskyi