Helping Enterprises Scale Their Jenkins Software Practices and Tools
summary
Gives ten enterprise best practices: vet every plugin in a staging instance first, run sample workloads after updates, avoid running builds on the master, provision slaves consistently via Puppet/Chef or Jenkins tool provisioning, and pilot with two–three teams to create local advocates and an executive sponsor. Recommends plugin set including job config plugin, audit trail, promoted builds and credentials plugin; cites deployments that support dozens of teams, hundreds of applications and thousands of builds per month and warns that inconsistent slave configs and unmanaged plugins cause major outages.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:22Context
- 5:27Common Concerns
- 8:32Plugins - Good, Bad and Useful
- 17:27Jenkins and Continuous Delivery
- 24:27Enterprise Security
- 26:43Example Security Segments
- 29:26Changing and Enterprise
related talks
37mHelping Enterprises Scale Their Jenkins Software Practices and Tools
34mHelping Enterprises Scale Their Jenkins Software Practices and Tools
42mSeven Habits of Highly Effective Jenkins Users
44mStairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins
33mMaking Strides towards Enterprise-Scale DevOps...w/ Jenkins in Your Tool Chain
33mJenkins 101
30mA Journey Introducing Jenkins to Enterprise IT
45mBuilding Your Continuous Delivery Toolkit