Implementing Modern CI in an IoT Medical Device
summary
Siemens Healthineers implements a production-grade CI for FDA/62304 embedded IoT medical devices that cuts release cycle friction by automating builds, static analysis, unit/mutation/integration tests, long-running performance runs (2–4 weeks), and artifact traceability via Jenkins + Artifactory. Pipelines use Jenkins Configuration-as-Code, Docker Swarm, parameterized multi-stage TX testing tiers, and publish versions with git tags; an Android test rig with emulators and a controller runs verification and performance tests. Continuous OSS checks use Software 360 for Automated OSS compliance and it works at scale.
AI-written summary · about
chapters (14)
- 0:00Introduction and background
- 1:57Siemens point of care project
- 4:02Defining CI quality gates
- 5:25Motivation and goals
- 7:14Building the CI pipeline
- 12:13Designing the feedback loops
- 15:38Jenkins infrastructure setup
- 19:51Parameterizing pipelines
- 23:15Managing software artifacts
- 27:54OSS compliance automation
- 31:33Automated testing environment
- 35:44Visualization and dashboards
- 39:11Future plans and summary
- 43:36Q&A session
related talks
43mContinuous Integration in IoT world - "Mission Impossible" or "A last hope"?
45mMulti-Stage-CI with Jenkins in an Embedded World
12mCi in IoT/Embedded: creating a simple, salable and automated workflow
33mHealthy CI for your product
35mMassively Continuous Integration: From 3 days to 30 minutes
45mCI Excellence With Test Automation Engineers
39mContinuous Security at the Next Level
32mBuilding Confidence Together: Continuous Integration & Testing