Field updates that can’t brick a device
- 18 releases
- A/B rollback
- Watchdog recovery
- Challenge
- A fleet of Raspberry Pi kiosks needed remote updates and provisioning, with nobody on site to recover a device when an update goes wrong.
- What we did
- We built the loader that looks after the kiosk software. It keeps two app slots and rolls back on its own when a new version keeps failing. Around it there’s a 21-step provisioning script you can safely run again, a systemd watchdog, and a Jenkins and Docker pipeline that checks every release before it goes out.
- Result
- 18 releases in 18 months, all rolled out remotely. If one fails, the kiosk rolls itself back.