Jenkins
The old workhorse — 1,800 plugins and it will build absolutely anything.
88
sovereigntyJenkins has been the default self-hosted CI server for well over a decade, and its plugin ecosystem is the largest in the category by a wide margin: whatever obscure toolchain, appliance or compliance step you need, someone has already written the plugin. It is MIT-licensed, endlessly extensible, and utterly unfashionable. Modern practice is declarative Jenkinsfiles rather than click-configured jobs, which removes most of the historical complaint about un-versioned build config, but it remains the heaviest thing here to operate.
OPEN SOURCEMITSELF-HOSTLOCAL-FIRST
LicenseMIT
PricingFree and open source. Commercial support available from CloudBees and others.
Open sourceYes
Self-hostableYes
Local-first dataYes
What it does well
- +The largest plugin ecosystem of any CI system, by far
- +Will drive hardware, legacy toolchains and on-prem estates nothing else touches
- +Mature, stable, and extremely well documented after twenty years
- +Commercial support exists if you need someone accountable
Where it falls short
- −Heaviest operational burden here — JVM tuning, plugin upgrades, drift
- −Plugin quality is uneven and security advisories are frequent
- −Dated interface and developer experience
- −Easy to end up with a snowflake controller nobody dares rebuild
Jenkins as an alternative to
Where Jenkins shows up in our comparisons, and how it ranked.
Jenkins head-to-head
Straight comparisons against the tools people weigh it against.