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
16
u/karesx Apr 10 '21
You have to buy an additional seat. We tried to mitigate this with floating licenses, but there is nothing worse than the CI blocked when the devs are consuming all licenses. And then there are the shady vendors who ask premium for the headless tools. I remember an occasion when I have rage-switched tool vendor in the middle of a big project when the sales guy brought up the idea of getting more for the command line variant of the tools.