Supply Chain Security with the Jenkins Templating Engine!
summary
Explains replacing per-repo Jenkinsfiles with a central Jenkins Templating Engine template plus plug‑in libraries so teams pick Maven or Gradle while the org enforces SonarQube scanning and signing/publishing artifacts. Shows concrete files (build.groovy, staticCode.groovy), hierarchical pipeline configs that merge at runtime, and real integrations with Anchore, Twistlock and OpenSCAP and Iron Bank images. Reports teams hit 50–75% adoption before complexity and maintainability break down.
AI-written summary · about
chapters (10)
- 0:00Supply Chain Security With The Jenkins Templating Engine!
- 1:37DevSecOps Overview
- 8:44Challenges in Scaling Adoption
- 13:44What Causes This Pain?
- 18:23Step 1: Defining our Software Delivery Process
- 19:49Step 2: Refactoring
- 21:39Making Libraries Reusable
- 23:13Hierarchical Pipeline Configurations
- 24:59JTE Mental Model
- 27:49Take Aways
related talks
29mTrusted Software Supply Chain with JTE
35mBuilding Reusable DevSecOps Pipelines on a Secure Kubernetes Platform
26mEverything You Should Be Doing, But Aren’t: DevSecOps for K8s Workflows
39mContinuous Security at the Next Level
26mMistakes Made Integrating Security Scanning into CI/CD
20mAI-Driven Security as Code in Jenkins
43mSecurity in DevOps Strategies
33mMaking Strides towards Enterprise-Scale DevOps...w/ Jenkins in Your Tool Chain