Professional Documents
Culture Documents
with SonarQube
HELLO!
I am Dmytro Patserkovskyi
Project Manager and Founder
of Dev SonarQube Community at V.I.Tech
Low code quality costs a lot
Toyota story
Aug. 28, 2009, San Diego CA, USA
Testable
Extendable & Covered with Tests
Code Metrics
Rules Violations
Code Style Bugs
checks if code compliant looking for bugs and
with conventions potential bugs
Performance
checks if everything
Vulnerabilities doing in the best way
search for bottlenecks
with lacks of validations,
security issues etc 100% - rules compliance
Code Coverage
Overall Coverage
Branch Coverage
!
I SHALL
NOT
DUPLICAT 0% - perfect solution
E ANY
1% - keep buffer
CODE ANY
Documentation
Quality Profile
Rules Plugins and Repositories
44 357
73
53
43
Quality Gates
Set of boolean conditions per project,
based on measure thresholds.
Passed
Warning
Failed
Quality Gates
Metric Operator
Open Issues Is greater than 70 100
Blocker Issues Is greater than 0
Critical Issues Is greater than 0
New Issues Is greater than 0 10
Overall Coverage Is less than 85 80
Unit Test Failures Is greater than 0
Quality of New Code
Each update
PullRequest
Nightly
Master branch
Support Team for SonarQube
Administrator
Setting up Dashboards
Upgrade
Monthly
Modifications Feedbacks
Monthly On-demand
24/7 monitoring and transparency
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
Questions
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