News for hackers. Stuff that matters.
Re:Write Gitlab CI Pipelines in Python Code by nly on Thursday April 29, 2021 @08:16PM (#26988453)
The problem in C++ land (my land) is all your dependencies are probably using different build systems.

Do you wan to migrate all your third party libs to Bazel, or just hack up a few lines of CI yaml to call the authors build system?

I lean on gitlab yaml quite heavily and it feels quite effortless

Re:Write Gitlab CI Pipelines in Python Code by vsgzusnex on Friday April 30, 2021 @02:09AM (#26990294)
We vendored all of our third party dependencies into our Bazel build. There were a lot and it was a giant PITA but over a multi-year horizon it was worth it. That doesn't mean it's the right choice for every business but it paid off for us.
Re:Write Gitlab CI Pipelines in Python Code by nly on Friday April 30, 2021 @08:29AM (#26992539)
Vendoring all your third party dependencies is fine, but you still have to build them.

Personally I use the native build system that upstream uses for most of them, and just hack in my compiler flags/options where necessary. Then I use CI triggers to rebuild my projects when the dependencies are rebuilt.