Dr. Jenkins M.D. at Your Service: An Overview of Jenkins at Cerner Corporation
summary
Cerner uses Jenkins as a core CI tool across desktop, server and mobile stacks, claiming nightly regression runs at 7:00 p.m., 81% of teams use Jenkins daily and 70% of jobs are automated builds. Engineers build an internal Jenkins job plugin (3–4 months to develop) to run UI test plans that take 10 minutes to 5 hours, plus a VM slave provisioning plugin that spins VMs in ~6–15 minutes. Mobile tests run on a Mac Mini cluster using Appium and TestFlight.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:12Agenda
- 1:36Who is Cerner
- 2:14Electronic Medical Records EMR
- 4:32Platforms
- 5:15Cerners use of Jenkins
- 5:44Development process
- 6:09Agile cycle
- 7:57Who uses Jenkins
- 8:35Solution Designers Engineers Delivery Consultants
- 10:08How frequently are you using Jenkins
- 10:46Breakdown usage of Jenkins
- 12:36Jenkins job plugin
- 13:11Jenkins job history
- 13:37Jenkins nightly jobs
- 14:05Jenkins nightly builds
- 14:34What else can we do
- 14:50Cloud Development
- 15:43Virtualization Farm
- 16:45Jenkins Slave Plugin
- 18:08Jenkins Slave Workflow
- 19:36Jenkins Environment Testing
- 20:33Mobile Development
- 21:57Mobile Testing Setup
- 23:26Mobile Testing Benefits
- 24:51More Frequent App Releases
- 25:08Better Bottom Line
- 26:06Jenkins Adoption Strategy
- 29:22Conclusion
related talks
30mDr. Jenkins M.D. at Your Service: An Overview of Jenkins at Cerner Corporation
50mJenkins in the Enterprise: Building Resilient CI Infrastructure
33mJenkins 101
42mJenkins: Enabling Agility and Efficiency
20mContinuous integration for mobile
35mMassively Continuous Integration: From 3 days to 30 minutes
35mJenkins Scaling and Organization for an Efficient CI
14mMobile CI at Etsy