gitlab-ci.yml, point it to GitLab CI’s docker executor, install and configure arduino-cli, download the same libraries that I used with Arduino IDE and voila! If it does what it says, I’ll simply need to draft a good old. However, Arduino IDE’s got its younger brother now – arduino-cli, which sounds like a silver bullet for my problem.

Yup, that window hungry and toolchain concealing tool, which I had no idea how to cross breed with windowless containerized build server. The thing that prevented me from adding CI in the past was Arduino IDE. So today I try to make the things right and for starters fix the CI part – if code hits the server, it should be built. However, being a consultant now, especially one who also specializes in CI/CD, makes that “ex web-developer” excuse invalid. Of cause, I could justify it by me being an ex web-developer, so any CI/CD and unit testing activities in Arduino IDE / ESP32 C++ project environment would be disturbingly unnatural. So anyway, despite the age, the project is backed by a quite a bit of code, which, though being maintained by GitLab server (basement edition), still has zero unit tests and equal amount of continuous integration. And the second – the guy’s just a few months old, give him a break. OK, he doesn’t look intimidating now, but first – it’s not the latest revision. Here he is, my ticket to the bright future:

The project is called “Jerry Annihilator” and it’s a robot that eventually will bring me a fame, a fortune, and a world domination. In fact, I’ve gotten myself into a new project which urges to be written about. But fear not – the blog is not dead! No sir.

Pip install brackets