What it does
Jenkins is an automation server whose Pipeline feature defines build, test, and delivery steps as code. A Jenkinsfile can live in source control with the application, making the automation visible in code review. Jenkins can be self-hosted and extended with plugins, which gives teams control over execution but makes installation, upgrades, plugin compatibility, and agent capacity part of their operations.
For a first Pipeline, the official guide walks through creating a Jenkinsfile and defining stages that execute shell or batch commands. Store that file in the repository so the build steps change alongside the application. A simple example might check out source, run a unit-test command, then package the result. Jenkins executes those steps on an agent; it does not supply the project's test expectations or maintain every external build dependency.
The tradeoff is operational ownership. Teams install and administer the Jenkins controller and its agents, and plugin choices affect the environment. The official repository license is MIT, but licensing does not remove the need to maintain the server and secure its credentials.
Strengths
- Pipeline definitions can be versioned as a Jenkinsfile in the source repository.
- The getting-started guide shows both UI-created and source-controlled pipelines.
- The core Jenkins repository is distributed under the MIT License.
Watch out for
- Self-hosting means the team maintains the controller, agents, plugins, and credentials.
Best for
- Teams that need to customize CI jobs and control where they execute
- Keeping build and deployment steps in a Jenkinsfile reviewed with application code
Sources
- Getting started with Pipeline (Oct 25, 2026)
- Jenkins License (Oct 25, 2026)