A topic that many embedded developers and teams are tackling today is how to manage their CI/CD pipelines. Continuous Integration (CI) makes a lot of sense because it focuses on building, testing, and validating the embedded software. But what about Continuous Deployment (CD)?
Continuously deploying embedded software at first sounds great, but do you really want to deploy new software to your customers continuously? Do your customers really want frequent updates if you are building automotive electronic control units (ECUs), medical devices, or even microwaves or home appliances?
This raises an interesting question for several teams: does continuous delivery for embedded products even make sense?
The purpose of continuous de
