Controlling Technical Debt With Continuous Delivery
summary
Shows how Fabric8 + Jenkins run pipeline-as-code to detect and incrementally check every commit, produce and apply machine-made patches via Walkmod/Maven goals, and push fixes back to Git so builds re-run automatically. Claims static rules are roughly 20–40% automatable, uses PMD, Checkstyle, FindBugs and SonarQube rule sets, and preserves local formatting while doing semantic fixes. Includes a reusable pipeline library and a live demo of patch generation and commit.
AI-written summary · about
chapters (7)
- 0:00Start
- 7:05How You Define a Pipeline
- 8:38Summary of What's Happened with Micro Services
- 14:57Sanity Check
- 19:59Common Bad Practices
- 20:51Sonarqube
- 25:28Semantic Analysis
related talks
04mContinuous Delivery with Jenkins' New Declarative Pipeline & Artifactory
44mStairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins
34mBeyond Continuous Delivery
01h 00mDeep Dive: Self-driving Pipelines: Building the Unbreakable Continuous...
29mContinuous Integration and Continuous Delivery Pipelines: Just the Basics
55mContinuous Deployment Workflows for Modern JavaScript
01h 29mBuilding a Continuous Delivery Pipeline with Gradle and Jenkins
28mContinuous Integration and Continuous Delivery Pipelines for Beginners and Managers