Dr. Jenkins M.D. at Your Service: An Overview of Jenkins at Cerner Corporation
summary
Cerner uses Jenkins as core CI to build and test complex EMR software, reporting 81% daily use and 70% automated builds / 65% automated tests; teams build two in-house extensions: an internal Jenkins plugins suite to schedule nightly regression runs (7pm) that turn 10-minute–to–5-hour manual tests into archived pass/fail jobs, and a VM-on-demand slaves plugin that provisions Windows VM slaves on demand; mobile pipelines use Appium + TestFlight on Mac mini device farms, yielding more frequent releases, fewer defects, and less tester time.
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
42mJenkins: Enabling Agility and Efficiency
30mA Journey Introducing Jenkins to Enterprise IT
33mJenkins 101
45mCI Excellence With Test Automation Engineers
27mWhy we provisioned 37 Jenkins servers...
34mHelping Enterprises Scale Their Jenkins Software Practices and Tools