Continuous Delivery for Embedded Systems
summary
Argues that continuous delivery practices can work for embedded systems but require specific fixes: use semantic versioning and stamp version into binary so shipped devices are reproducible; prefer one long‑lived branch and build binaries once; replace expensive proprietary toolchains with GCC/free OS/ARM where possible; automate builds with Jenkins + job DSL and keep hardware-in-the-loop system tests (example: automated radar lab with rotating ball bearings and Lego); cites OTA updates (Tesla) and recalls (1.4M Fiat Chrysler) as real consequences.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:17Software Development Process
- 5:48Continuous Delivery
- 8:26Challenges
- 14:05Versioning
- 20:26Testing
- 29:29Security
- 30:59QA
related talks
45mTurning continuous delivery into competitive business advantage
47mContinuous Acceleration: Why Continuous Everything Requires A Suppl...
33mContinuous Delivery - What does good really look like?
24mWhy, What, and How of Continuous Delivery
40mContinuous Delivery Anti-Patterns
32mContinuous Delivery Sounds Great But It Won’t Work Here
46mHow to architect for continuous delivery?
05mDo this, not that: Antipatterns in Continuous Deployment