Jenkins
In one line
Jenkins is an open-source automation server that helps build, test, and deploy code through configurable pipelines.
In simple words
Jenkins is one of the oldest and most widely used CI/CD tools. It is a self-contained automation server that runs on Java and provides a web interface for defining and running pipelines.
You define pipelines in a Jenkinsfile — either as declarative or scripted pipeline syntax. A pipeline consists of stages like "Build", "Test", "Deploy". Jenkins executes each stage and shows the results in a visual dashboard.
Jenkins has a huge ecosystem of plugins (over 1,500) that integrate with almost any tool — Git, Docker, Kubernetes, AWS, Slack, etc. This flexibility makes it powerful but also means it requires more maintenance than newer CI/CD tools.
Example
pipeline {
agent any
stages {
stage('Build') {
steps { sh 'npm run build' }
}
stage('Test') {
steps { sh 'npm test' }
}
stage('Deploy') {
steps { sh 'kubectl apply -f k8s/' }
}
}
}This Jenkinsfile defines a pipeline with three stages: build, test, and deploy to Kubernetes.
How it works
- You define a pipeline in a Jenkinsfile (in your repo or in Jenkins).
- Jenkins detects a code change (via webhook or polling).
- It runs the pipeline stages on an agent (build, test, deploy).
- Results are shown in the Jenkins dashboard with logs and status.
Common confusions
Confused with: GitHub Actions
The difference: Jenkins is a self-hosted server that requires maintenance; GitHub Actions is a managed service built into GitHub with no server to maintain.
Related terms
Decode error messages
Plain-English explanations of common errors — what they mean, why they happen, and how to fix them.