Improving Software Quality with Jenkins
summary
Jenkins job runs a post‑build scan that cracks open the war, fingerprints jars and queries a cloud service to produce a component report; a tiny demo app reveals 57 components, 2 security alerts and 18 license alerts, and a historic case shows 7,000 organizations downloading a fixed vulnerable bouncy castle three years after the patch. Results surface an Insight plugin that can fail the build, show observed versus declared licenses in Nexus, and point to actionable upgrades.
AI-written summary · about
chapters (21)
- 0:00Start
- 0:07Improving Software Quality Using Component Lifecycle Management with Jenkins
- 3:44Exploding Component Usage Example Central Repository
- 4:57Open Source Is Everywhere
- 5:27The Move To Component-Based Software Development Things are now possible, that seemed impossible before, but we need to
- 6:36An Immature Ecosystem
- 9:50Complicating Factors
- 10:35Security - bouncycastle
- 12:37Intellectual Property Licensing
- 15:16Open Source Benefits → Come with Risks
- 17:05Find it Early, Fix it Early
- 17:33How can we deal with this?
- 20:53Insight For CI Plugin - Configuration • Find it in Plugin Manager • Global Settings
- 21:12Insight For CI Plugin - What it does
- 30:14Security And License Issues
- 32:26Insight App Health Check
- 34:00CLM Stages - Inventory
- 34:20CLM Stages - Analyze
- 35:01CLM Stages - Monitor
- 35:53Requirements for CLM
- 37:16What next?
related talks
39mContinuous Security at the Next Level
11mIdentifying Security Vulnerabilities at Scale: Venture Inside a Pipeline
42mJenkins: Enabling Agility and Efficiency
29mTrusted Software Supply Chain with JTE
20mAI-Driven Security as Code in Jenkins
33mJenkins 101
42mZero to Jenkins: Automatic builds + deploys
35mJenkins Scaling and Organization for an Efficient CI