4 ms·

What would people recommend for a self-hosted CI system in 2023? I'm currently leaning towards Jenkins, because neighboring teams are using it (with some pain

What would people recommend for a self-hosted CI system in 2023? I'm currently leaning towards Jenkins, because neighboring teams are using it (with some pain due to their scale, but theirs is 10x-100x ours), and I have some ~10y-old experience with it. (Our builds are compiling for embedded targets, with a Makefile-based system)

AceJohnny2 3y ago
I've noticed the Avahi folks use Woodpecker CI [1], which I hadn't heard of before, because it supports priorities and pre-emption [2] [1] https://woodpecker-ci.org/ https://woodpecker-ci.org/ [2] https://social.treehouse.systems/@marcan/111258515328251078 https://social.treehouse.systems/@marcan/111258515328251078
kbenson 3y ago
Because not every company wants to allow their source code to the cloud. Basically all the reasons organization self host their code repositories (and a bunch do) all apply.
- AceJohnny2 3y ago
  Note that I asked "what" do people recommend, not "why" do people recommend...
danielheath 3y ago
Buildkite is mixed-hosting; source code stays on your machines, on-prem if you like, but build logs / history / SCM triggers are hosted. Unclear whether that’s enough for your situation but it’s by far my favourite because of how it lets you store the CI pipeline in the repository (so changes are reviewed via normal channels etc).
MilStdJunkie 3y ago
You can run a local gitlab instance, so I'd assume self-hosting as a rider on that. Unless I've been making some very bad mistakes. GitLab's not too bad. I had a Gradle pile I had been using but once I knocked out some old Java bits I wanted to sleek my "required tools" down a bit. I've integrated some OpenProject stuff into GL also. Maybe someday . . for "minimal" clients . . I can just bring in the GitLab and call it a day, so far as server stuff is concerned. That day is not today, however. Customers in my business want a lot - like, a LOT a lot - of project toys, and homebrewing those in GitLab is beyond my skills.
shitcoder 3y ago
I use drone self hosted (which is what Woodpecker CI was forked from in one of the other replies). It's an alright system and it works with my Gitea instance to build executables and docker images. I think though ironically my take away after setting everything up, was that I didn't really need to spend a lot of time to get it perfect, rather just getting it working was enough for me.
cvalka 3y ago
https://docs.gitea.com/usage/actions/overview https://docs.gitea.com/usage/actions/overview https://github.com/agola-io/agola https://github.com/agola-io/agola https://github.com/concourse/concourse https://github.com/concourse/concourse https://github.com/theSage21/jaypore_ci https://github.com/theSage21/jaypore_ci https://github.com/woodpecker-ci/woodpecker https://github.com/woodpecker-ci/woodpecker

AceJohnny2 3y ago

I've noticed the Avahi folks use Woodpecker CI [1], which I hadn't heard of before, because it supports priorities and pre-emption [2] [1] https://woodpecker-ci.org/ https://woodpecker-ci.org/ [2] https://social.treehouse.systems/@marcan/111258515328251078 https://social.treehouse.systems/@marcan/111258515328251078

kbenson 3y ago

Because not every company wants to allow their source code to the cloud. Basically all the reasons organization self host their code repositories (and a bunch do) all apply.

AceJohnny2 3y ago
Note that I asked "what" do people recommend, not "why" do people recommend...

danielheath 3y ago

Buildkite is mixed-hosting; source code stays on your machines, on-prem if you like, but build logs / history / SCM triggers are hosted. Unclear whether that’s enough for your situation but it’s by far my favourite because of how it lets you store the CI pipeline in the repository (so changes are reviewed via normal channels etc).

MilStdJunkie 3y ago

You can run a local gitlab instance, so I'd assume self-hosting as a rider on that. Unless I've been making some very bad mistakes. GitLab's not too bad. I had a Gradle pile I had been using but once I knocked out some old Java bits I wanted to sleek my "required tools" down a bit. I've integrated some OpenProject stuff into GL also. Maybe someday . . for "minimal" clients . . I can just bring in the GitLab and call it a day, so far as server stuff is concerned. That day is not today, however. Customers in my business want a lot - like, a LOT a lot - of project toys, and homebrewing those in GitLab is beyond my skills.

shitcoder 3y ago

I use drone self hosted (which is what Woodpecker CI was forked from in one of the other replies). It's an alright system and it works with my Gitea instance to build executables and docker images. I think though ironically my take away after setting everything up, was that I didn't really need to spend a lot of time to get it perfect, rather just getting it working was enough for me.

cvalka 3y ago

https://docs.gitea.com/usage/actions/overview https://docs.gitea.com/usage/actions/overview https://github.com/agola-io/agola https://github.com/agola-io/agola https://github.com/concourse/concourse https://github.com/concourse/concourse https://github.com/theSage21/jaypore_ci https://github.com/theSage21/jaypore_ci https://github.com/woodpecker-ci/woodpecker https://github.com/woodpecker-ci/woodpecker