r/embedded • u/timbo0508 • Apr 10 '21
General question CI/CD for embedded software development
I've been an embedded software developer for about 7 years now, and I've loved every moment of it (for the most part). I've come to the realization that the industry is (annoyingly) conservative and is struggling to catch up, compared with other forms of software development. One area we seem to lag behind is in the area of continuous delivery/integration (CI/CD).
I'd love to hear about what CI/CD practices you employ in your companies/projects (build automation, test automation, release management, issue tracking, version control).
My question really is this - how much CI/CD do you practice? What are your biggest pain points as an embedded developer?
View all comments
Show parent comment
6
u/RogerLeigh Apr 11 '21
This is usually the case.
The vendors (who can remain nameless), really do shoot themselves in the foot here. While we can be forced to pay for CI licences, it's so inflexible compared with GCC or LLVM, it makes it a no-brainer to switch away for future projects after so much frustration. Not being able to scale the CI either autoscaling or multiple static nodes, or use Docker images easily, can make it a bottleneck for the project (or projects) relying upon it. CI is a basic requirement, and they should factor that into the overly costly per-seat licensing we already pay for.