What is CI? DRY CI So I have talked before about what CI actually means. That post was, admittedly, rather dry and academic. I think it’s important to sometimes make the distinction between what is just regular automation and what is strictly CI. When there is automation but no CI it is still very easy for errors to slip into a supposedly stable code base, as not every commit is tested before it is merged to the main.
What is CI? DRY CI At work I have been doing CI for nearly 10 years, now. Having been working at Red Hat for the past 6 of those, some of the CI work that I do is available in open source contributions up on Git Hub. I plan to make a series of posts about that work, so I am going to start with this brief discussion of the very idea of CI before I get into working on the particular types of CI that I do.
So I recently grabbed a PinePhone, because my old Galaxy S9+ has been dying a slow death. The old one started out being finnicky about docking to the car, then charging became an intermittent hassle, then the screen started to die slowly. So it was time to get a replacement. Might as well go with something very different and out of place, eh? Why not take a look at the only generally available smartphone that was running an upstream version of Linux?