What is Jenkins?
Jenkins began as Hudson in 2004 and was renamed Jenkins in 2011 after a licensing and trademark dispute with Oracle split the community. It is now stewarded under the Continuous Delivery Foundation (part of the Linux Foundation). Jenkins runs on a controller/agent architecture: the controller schedules and tracks jobs, while agents (static or dynamically provisioned) execute the actual build and test steps.
Read the full overview
Pipelines are typically defined as code in a Jenkinsfile checked into the repository, using Jenkins's declarative or scripted Pipeline syntax. Functionality beyond the core is added through plugins - for source control, cloud providers, notification channels, and deployment targets.
Sources checked 27 September 2026: Pipeline documentation, architecture overview.
JenkinsCI/CDOpen-source automation server for build, test, and deployment pipelines
Key capabilities
- Pipeline as code: Define build, test, and deploy stages in a versioned Jenkinsfile.
- Plugin ecosystem: Extend Jenkins with integrations for source control, cloud, and notification tools.
- Distributed builds: Run jobs across static or dynamically provisioned agents.
- Self-hosted control: Operate the controller and agents on your own infrastructure.
Where Jenkins fits
Plan controller upgrades, agent provisioning, and plugin patching as ongoing maintenance work, not one-time setup. Keep pipeline definitions in version control alongside the code they build.
Positioning and limitations
Choose Jenkins when a team wants full control over its CI/CD infrastructure and is willing to operate and patch the controller and agents itself. Its plugin ecosystem covers most integrations, but plugin maintenance and security updates become an ongoing responsibility as the install grows.
A solid pilot builds a real branch through a Jenkinsfile pipeline, provisions an agent to run it, and confirms the team can keep plugins and the controller patched without a dedicated full-time maintainer.
“Open-source automation server for build, test, and deployment pipelines”
Technical details
- Access
- Self-hosted
- Source model
- Open source
- License
- Verify license
- Founded
- 2011
- Headquarters
- Open Source Project
- Pricing model
- Open source
- API
- Available
- Version reference
- jenkins-2.583 ↗
- Source checked
- September 27, 2026
- Website
- www.jenkins.io ↗
- GitHub
- Source repository ↗
What to verify
Start from the users, systems and operating responsibilities the tool needs to support.
- Confirm current features, licensing and support terms.
- Validate deployment, data location and access control.
- Test integrations, exports and recovery workflows.
Reviews of Jenkins
No published reviews yet.
Loading review form…
