A Journey Introducing Jenkins to Enterprise IT
summary
Target introduces Jenkins to run CI across ~30 separate APIs, grows adoption from one team to dozens, and uses Job DSL to auto-create jobs, Artifactory for jars, Chef + OpenStack to spin fresh test environments per run, and performance and security hooks (short perf hammers, ZAP scans). They add role-based folders, plugin analytics and Jenkins Operations Center for multi-master scale, automate PagerDuty/Splunk/RunScope via APIs, and report enough efficiency and reliability gains to justify Jenkins Enterprise and paid support.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 0:56Target API
- 1:34Location API
- 2:34Patch Changes
- 3:40Why Jenkins
- 4:55Change Habits
- 7:26Functional Cases Test Cases
- 8:23Onboarding API Jobs
- 9:40Code Coverage
- 10:27Performance Tests
- 12:12API Blueprints
- 13:33Infrastructure is Code
- 14:17Environments
- 15:46Deployments
- 18:35Monitoring Tools
- 19:05Pull Requests
- 19:59Vulnerability Testing
- 20:20promoted builds plugin
- 20:39chat ops plugin
- 21:37Jenkins Operations Center
- 21:49Jenkins Spreads
- 23:09The Conversation
- 26:38Adoption
- 27:00Job Folders
- 28:17Support
- 28:47Operation Center
- 29:27Hiring
related talks
30mA Journey Introducing Jenkins to Enterprise IT
34mHelping Enterprises Scale Their Jenkins Software Practices and Tools
33mMaking Strides towards Enterprise-Scale DevOps...w/ Jenkins in Your Tool Chain
50mJenkins in the Enterprise: Building Resilient CI Infrastructure
27mWhy we provisioned 37 Jenkins servers...
33mJenkins 101
47mJenkins in the Enterprise: Building Resilient CI Infrastructure
23mMoving from Jenkins to Jenkins X: Scaling and Accelerating CI/CD