What is
Jenkins
?
Most platform initiatives fail the same way: they start too big, get funded like projects instead of products, build for too long without testing with users, and confuse renaming an infrastructure team with building a platform team. Instead, start small, learn fast and scale deliberately.
At a glance
Field | Value |
|---|---|
Primary use case | Automating software builds, tests, and continuous delivery pipelines |
Deployment type | Self-hosted Java application; native packages, WAR, or container deployment |
Pricing model | Free/open source; hosting infrastructure costs apply |
Supported integrations | Git, GitHub, Perforce Helix Core, SonarQube, Gitea, Kubernetes, Docker |
Source type | Open |
Cloud provider | Cloud Agnostic |
Ideal team size | Small teams to large enterprises |
Required skills | Java runtime installation, server administration, CI/CD pipeline engineering, Git, Groovy scripting, plugin configuration |
AEP branch | Tooling |
AEP category | Integration & Delivery |
AEP subcategory | CI |
Profile
CI is the most specific AEP level for Jenkins. Jenkins is an extensible, open-source automation server that can run as a simple CI server or serve as a continuous delivery hub. Its Java-based application is available in packages for Windows, Linux, macOS, and other Unix-like operating systems.
Jenkins can be configured through a web interface with on-the-fly error checks and built-in help. Its plugin architecture supports integrations across the continuous integration and continuous delivery toolchain, and it can distribute work across multiple machines.
Focus
Jenkins serves teams ranging from small groups to large enterprises that need to automate software builds, tests, and continuous delivery pipelines. It addresses the need to coordinate these activities across projects and, when needed, distribute builds, tests, and deployments across multiple machines.
Background
Jenkins is described in the available research as a community-driven, open-source project. The research does not specify its founding date, funding, or corporate history.
The project invites community contributions to code, documentation, localization, blog posts, artwork, and meetups.
Features
Cross-platform Java application
Jenkins provides a self-contained Java-based program for running automation. This lets teams install it on supported operating systems using packages for Windows, Linux, macOS, and other Unix-like systems.
Web-based configuration
Jenkins can be set up and configured through its web interface. The interface provides on-the-fly error checks and built-in help to support configuration.
Plugin architecture
Jenkins can be extended to support different automation and integration needs. Its plugin architecture and Update Center provide access to hundreds of plugins for tools across the CI/CD toolchain.
Distributed execution
Jenkins can distribute work across multiple machines. This supports running builds, tests, and deployments across multiple platforms.
Pros and cons
Pros
Open-source software with no Jenkins software license cost.
Hundreds of plugins and an extensible architecture support integrations across the CI/CD toolchain.
Work can be distributed across multiple machines and platforms.
Available as packages for Windows, Linux, macOS, and other Unix-like operating systems.
Cons
Jenkins is self-hosted, so teams must provide and administer hosting infrastructure; infrastructure costs apply even though the software is free.
Installation and operation can require Java runtime installation and server administration, while pipeline implementation may require CI/CD engineering, Git, Groovy scripting, and plugin configuration.
FAQs
Jenkins FAQs
How does Jenkins work?
Jenkins runs as a Java-based automation server. Teams configure Jenkins through its web interface, extend it with plugins, and can distribute work across multiple machines.
What tools does Jenkins integrate with?
Jenkins supports integrations with Git, GitHub, Perforce Helix Core, SonarQube, Gitea, Kubernetes, Docker.
How much does Jenkins cost?
Jenkins has a pricing model of Free/open source; hosting infrastructure costs apply.
Is Jenkins a CI/CD tool?
Jenkins is classified as CI in the Tooling branch and can run as a simple CI server or as a continuous delivery hub.
What is required to run Jenkins?
Jenkins is a self-hosted Java application; native packages, WAR, or container deployment are listed deployment options. The listed required skills are Java runtime installation, server administration, CI/CD pipeline engineering, Git, Groovy scripting, plugin configuration.
