Description
Every merge means somebody pulls the code, runs the tests, builds the package and pushes it to a server by hand — and any forgotten step bites. That list was never meant to live in a person’s head.
Jenkins is the automation server that takes the pipeline over: a commit triggers a build, tests run and report, and a passing build deploys itself. It has been around since 2004, is written in Java, free and open source, and its ecosystem has over a thousand plugins — Git, Docker, Kubernetes, the cloud platforms and the notification channels are all a plugin away.
Pipelines are written as a Jenkinsfile that lives in the repository and is versioned with the project. There are LTS and weekly release lines, with installers for Windows, macOS, Linux and Docker.
Pipeline as code: describe every build, test and deploy step in a Jenkinsfile — reviewable, reusable, in the repo.
Plugin ecosystem: over a thousand plugins for SCM, build tools, test reports, deployment targets and notifications.
Distributed builds: fan jobs out to multiple agents in parallel, with each platform building on its own kind of machine.
Flexible triggers: commits, schedules, upstream jobs or a manual click.
LTS and weekly: LTS baselines every 12 weeks with fix releases every 4 weeks; weekly builds for the newest features.
Jenkins is the automation server that takes the pipeline over: a commit triggers a build, tests run and report, and a passing build deploys itself. It has been around since 2004, is written in Java, free and open source, and its ecosystem has over a thousand plugins — Git, Docker, Kubernetes, the cloud platforms and the notification channels are all a plugin away.
Pipelines are written as a Jenkinsfile that lives in the repository and is versioned with the project. There are LTS and weekly release lines, with installers for Windows, macOS, Linux and Docker.
Features
Pipeline as code: describe every build, test and deploy step in a Jenkinsfile — reviewable, reusable, in the repo.
Plugin ecosystem: over a thousand plugins for SCM, build tools, test reports, deployment targets and notifications.
Distributed builds: fan jobs out to multiple agents in parallel, with each platform building on its own kind of machine.
Flexible triggers: commits, schedules, upstream jobs or a manual click.
LTS and weekly: LTS baselines every 12 weeks with fix releases every 4 weeks; weekly builds for the newest features.
