Continuous Delivery of IoT Sensors
summary
Drogue IoT proves continuous delivery for tiny MCUs by wiring cloud CI/CD to device bootloaders and gateways: it uses Tekton build pipeline plus container registries or Eclipse hawkBit, Apache Kafka for telemetry, and MQTT/CoAP/HTTP transports, and demonstrates OTA over BLE to a micro:bit that keeps reporting temperature while swapping images and switching from blink A to blink B. Devices use an active–passive bootloader with rollback and negotiate block size; note bandwidth limits (example: 64 KB in 4 days on LoRaWAN).
AI-written summary · about
chapters (18)
- 0:00Start
- 2:15Continuous what?
- 4:05Target hardware
- 4:54Bugs
- 5:09Critical updates
- 5:36Factors considered
- 8:05Reducing risk
- 9:12Resource usage
- 10:50Tooling
- 11:29Sensor Firmware
- 13:23Connectivity: Drogue Cloud
- 15:11Management: Drogue Cloud
- 15:43Firmware Build & Delivery
- 17:57Console
- 18:32Build overview
- 18:55Demo
- 34:12Recap
- 35:49Try it yourself
related talks
36mContinuous Deployment of IoT Sensors
28mContinuous Integration of C/C++ Apps for IoT Devices
38mAutomating and Managing an IoT Fleet Using Git
52mCreating Continuous Delivery for Yocto Based IoT Distribution
37mContinuous Delivery for Embedded Systems
12mCi in IoT/Embedded: creating a simple, salable and automated workflow
30mOffline IoT - Building Resilient Connected Devices without the Internet
27mIoT is hard, keep hustling