Build Breakers, Not Gatekeepers (DevOpsCon Munich 2020 - Keynote)

BUILD BREAKERS! NOT GATEKEEPERS MICHIEL ROOK @MICHIELTCS

@michieltcs TRADITIONAL SOFTWARE DEV

@michieltcs

@michieltcs HUMAN GATEKEEPERS

@michieltcs HANDOFFS

@michieltcs COSTLY

@michieltcs WASTEFUL

@michieltcs DOESN'T SCALE

@michieltcs

@michieltcs CONTINUOUS & MANY SMALL CHANGES

@michieltcs SHIFT LEFT

@michieltcs ELIMINATE ISSUES EARLY

@michieltcs

@michieltcs HOW?

@michieltcs AUTOMATION

@michieltcs Source: 2017 State Of DevOps report @michieltcs

@michieltcs 60 Accelerate: State of DevOps 2019 | How Do
We Improve Productivity? As Martin Fowler outlines,33 companies should be thoughtful about which so ware is strategic and which is merely utility. By addressing their utility needs with COTS solutions and minimizing customization, high performers save their resources for strategic so ware development e orts. We also see that elite performers automate and integrate tools more frequently into their toolchains on almost all dimensions. Although automation may be seen as too expensive to implement (we o en hear, “I don’t have time or budget to automate— it’s not a feature!”), automation is truly a sound investment.34 It allows engineers to spend less time on manual work, thereby freeing up time to spend on other important activities such as new development, refactoring, design work, and documentation. It also gives engineers more confidence in the toolchain, reducing stress in pushing changes. 33 Martin Fowler, MartinFowler.com, UtilityVsStrategicDichotomy. https://martinfowler.com/bliki/UtilityVsStrategicDichotomy.html 34 This is a site reliability engineering (SRE) best practice: reduce toil, which is work without productivity. Low Medium High Elite Automated build 64% 81% 91% 92% Automated unit tests 57% 66% 84% 87% Automated acceptance tests 28% 38% 48% 58% Automated performance tests 18% 23% 18% 28% Automated security tests 15% 28% 25% 31% Automated provisioning and deployment to testing environments 39% 54% 68% 72% Automated deployment to production 17% 38% 60% 69% Integration with chatbots / Slack 29% 33% 24% 69% Integration with production monitoring and observability tools 13% 23% 41% 57% None of the above 9% 14% 5% 4% AUTOMATION AND INTEGRATION BY PERFORMANCE PROFILE Source: 2019 State Of DevOps report

@michieltcs BUILD BREAKERS

@michieltcs AUTOMATED QUALITY GATES

@michieltcs FAIL

@michieltcs WARN

@michieltcs PASS

@michieltcs WARN PASS FAIL

@michieltcs PIPELINES

@michieltcs DEV BUILD / TEST CONTINUOUS INTEGRATION

@michieltcs BUILD BUILD BREAKERS WARN PASS FAIL WARN PASS FAIL
WARN PASS FAIL WARN PASS FAIL

@michieltcs TIME TO ZOOM IN

@michieltcs CODE QUALITY & STANDARDS

@michieltcs phpcs --standard=PSR12 src CODE STYLE (PHPCS, Checkstyle)

@michieltcs STATIC ANALYSIS (Findbugs, PHPStan)

@michieltcs TESTING

@michieltcs @michieltcs UNIT TESTS E2E / VISUAL TESTS INTEGRATION TESTS
LOTS OF MANUAL TESTING E2E TESTS

@michieltcs @michieltcs UNIT TESTS E2E TESTS INTEGRATION TESTS COST SPEED

@michieltcs @michieltcs UNIT TESTS E2E TESTS INTEGRATION TESTS Exploratory testing
& user feedback Monitoring & alerting COST SPEED

@michieltcs @michieltcs UNIT TESTS E2E TESTS INTEGRATION TESTS Exploratory testing
& user feedback Monitoring & alerting COST SPEED 70% 20% 10%

@michieltcs UNIT TESTS (PHPUnit, JUnit, TestNG)

@michieltcs CODE COVERAGE

@michieltcs INTEGRATION TESTS (PHPUnit*, Spring TestContext, RestAssured)

@michieltcs @michieltcs UI TESTING (Cypress, Selenium)

@michieltcs @michieltcs CONTRACT TESTING (Pact, Dredd)

@michieltcs SECURITY

@michieltcs DEPENDENCY SCANNING & UPDATING

@michieltcs @michieltcs

@michieltcs @michieltcs GITHUB INTEGRATION (Renovate, Dependabot)

@michieltcs VULNERABLE DEPENDENCIES (Snyk, Whitesource, Nexus)

@michieltcs STATIC APPLICATION SECURITY TESTING

@michieltcs SAST (Fortify, RIPS, Sonarqube, Coverity)

@michieltcs CONTAINERS & IMAGES

@michieltcs CONTAINER IMAGE SCANNING (Clair, Twistlock)

@michieltcs PERFORMANCE

@michieltcs PERFORMANCE TESTS (JMeter, Gatling, Locust)

@michieltcs 1. DETERMINE BASELINE 2. AGREE ON SOFT / HARD
LIMITS 3. RUN IN PIPELINE TO CALC % UP/DOWN

@michieltcs OTHER AREAS

@michieltcs MUTATION TESTING

@michieltcs APPROVALS & WORKFLOWS

@michieltcs ACCESSIBILITY

@michieltcs DEPLOYMENTS

@michieltcs ....

@michieltcs TIPS

@michieltcs AVOID FLAKEY TESTS

@michieltcs NO TEST SUITE DETECTS EVERY ISSUE

@michieltcs WATCH YOUR BUILD TIME

@michieltcs ENSURE FAST FEEDBACK

@michieltcs @michieltcs

@michieltcs FEEDBACK!

@michieltcs NOW YOU

@michieltcs AGREE ON STANDARDS

@michieltcs BUILD A PIPELINE

@michieltcs TAKE SMALL STEPS

@michieltcs LET'S TURN GATEKEEPERS INTO BUILD BREAKERS!

@michieltcs THANK YOU FOR LISTENING! @michieltcs / [email protected] www.michielrook.nl

Build Breakers, Not Gatekeepers (DevOpsCon Muni...

Build Breakers, Not Gatekeepers (DevOpsCon Munich 2020 - Keynote)

More Decks by Michiel Rook

Other Decks in Programming

Featured

Transcript