cimaster

We’re considering switching from Jenkins to GitHub Actions as our primary CI system. We’re planning to run self-hosted runners on the same infrastructure we’ve been using with Jenkins.

So far, my experience with GitHub Actions has been positive—honestly, using anything other than Jenkins feels like an improvement. That said, I’ve run into a few challenges, particularly around the interface and some missing features compared to more traditional CI systems. For instance, there’s no clear way to view a queue of pending jobs across the repository, triggering a build for a historical commit isn’t straightforward (unless you set up dispatch parameters manually), and there’s no built-in test result tracking.

Managing self-hosted runners also requires setup and monitoring, whereas Jenkins provides a lot of this out of the box.

For context, we’re a fairly typical company with around 150 developers and a few dozen repositories.

Has anyone here been through a similar transition? Any advice or insights?

I'm evaluating CI tools for projects hosted on GitHub in a medium-sized enterprise. Looking at CircleCI, Jenkins, Bamboo, GitHub Actions, and Buildkite.

Since GitHub Actions is the default option, everything else is essentially being compared to it. But none of them really stand out—most have some limitations when working with GitHub, while GHA itself feels pretty barebones, requiring extra work to build out missing features (like proper test reporting).

For those who’ve worked with CI and GitHub, what’s been your best experience? Any lessons learned or recommendations?