Last updated: 10 November 2026
Jenkins can do almost anything, but only because of its plugins. This list picks 30 plugins that most CI/CD setups actually use, grouped by job: source control, pipelines, build and deploy, security, code quality, notifications and administration. Each one has its plugin ID and an install command, so you can copy it straight into your setup.
New to Jenkins? Start with What is Jenkins?

What Are Jenkins Plugins?
Plugins are add-ons that extend Jenkins core. They add integrations (Git, Docker, Kubernetes, Slack), pipeline steps, security features and UI views. Jenkins has around 2,000 plugins in its update centre. Each plugin has a short plugin ID (for example git or slack) that you use when installing it from the command line.
Quick Picks
- Must-have for every server: Pipeline, Git, Credentials Binding, Configuration as Code, Timestamper.
- For containers and Kubernetes: Docker Pipeline, Kubernetes.
- For code quality: SonarQube Scanner, Warnings Next Generation, JUnit.
- For security: Role-based Authorization Strategy, HashiCorp Vault.
- For team visibility: Slack Notification, Pipeline Graph View.
Source Control Plugins
1. Git
- Plugin ID:
git - What it does: Clones, fetches and checks out Git repositories, and adds the
gitandcheckout scmsteps. - Install:
jenkins-plugin-cli --plugins git
2. GitHub Branch Source
- Plugin ID:
github-branch-source - What it does: Discovers repos, branches and pull requests in a GitHub organization and creates multibranch pipelines for them, with build status sent back to GitHub.
- Install:
jenkins-plugin-cli --plugins github-branch-source
3. GitLab
- Plugin ID:
gitlab-plugin - What it does: Triggers builds from GitLab webhooks (push and merge request) and reports build status back to GitLab.
- Install:
jenkins-plugin-cli --plugins gitlab-plugin
4. Bitbucket Branch Source
- Plugin ID:
cloudbees-bitbucket-branch-source - What it does: Multibranch and organization folder support for Bitbucket Cloud and Bitbucket Data Center.
- Install:
jenkins-plugin-cli --plugins cloudbees-bitbucket-branch-source
Pipeline Plugins
5. Pipeline
- Plugin ID:
workflow-aggregator - What it does: Installs the full Pipeline suite so you can write
Jenkinsfilepipelines, including multibranch pipelines. - Install:
jenkins-plugin-cli --plugins workflow-aggregator
6. Pipeline Graph View
- Plugin ID:
pipeline-graph-view - What it does: A modern graph of stages and steps with logs per step. It is the recommended replacement for Blue Ocean.
- Install:
jenkins-plugin-cli --plugins pipeline-graph-view
7. Pipeline Utility Steps
- Plugin ID:
pipeline-utility-steps - What it does: Adds steps such as
readJSON,readYaml,writeJSON,zipandfindFiles. - Install:
jenkins-plugin-cli --plugins pipeline-utility-steps
8. Job DSL
- Plugin ID:
job-dsl - What it does: Creates jobs and folders from Groovy scripts kept in Git, so you never click jobs together by hand.
- Install:
jenkins-plugin-cli --plugins job-dsl
9. Configuration as Code (JCasC)
- Plugin ID:
configuration-as-code - What it does: Configures Jenkins itself (security, credentials, clouds, tools) from a YAML file. See the JCasC example below.
- Install:
jenkins-plugin-cli --plugins configuration-as-code
Build and Deployment Plugins
10. Docker Pipeline
- Plugin ID:
docker-workflow - What it does: Lets pipelines build images, push them and run steps inside containers with
docker.build()anddocker.image().inside {}. - Install:
jenkins-plugin-cli --plugins docker-workflow
11. Kubernetes
- Plugin ID:
kubernetes - What it does: Starts a fresh agent pod for each build in a Kubernetes cluster and removes it afterwards, so you only pay for agents while they run.
- Install:
jenkins-plugin-cli --plugins kubernetes
12. Amazon EC2
- Plugin ID:
ec2 - What it does: Starts EC2 instances as build agents on demand and stops them when idle.
- Install:
jenkins-plugin-cli --plugins ec2
13. SSH Agent
- Plugin ID:
ssh-agent - What it does: Makes SSH keys from Jenkins credentials available to
ssh,scpandgitcommands inside asshagent {}block. - Install:
jenkins-plugin-cli --plugins ssh-agent
Security and Credentials Plugins
14. Credentials
- Plugin ID:
credentials - What it does: Stores passwords, tokens, SSH keys and certificates encrypted in Jenkins.
- Install:
jenkins-plugin-cli --plugins credentials
15. Credentials Binding
- Plugin ID:
credentials-binding - What it does: Exposes credentials to a pipeline as masked environment variables with
withCredentials. - Install:
jenkins-plugin-cli --plugins credentials-binding
16. Role-based Authorization Strategy
- Plugin ID:
role-strategy - What it does: Global, folder and agent roles so teams only see and run their own jobs.
- Install:
jenkins-plugin-cli --plugins role-strategy
17. Matrix Authorization Strategy
- Plugin ID:
matrix-auth - What it does: A grid of permissions per user or group, globally or per job.
- Install:
jenkins-plugin-cli --plugins matrix-auth
18. HashiCorp Vault
- Plugin ID:
hashicorp-vault-plugin - What it does: Reads secrets from Vault at build time instead of storing them in Jenkins.
- Install:
jenkins-plugin-cli --plugins hashicorp-vault-plugin
Code Quality and Testing Plugins
19. JUnit
- Plugin ID:
junit - What it does: Publishes JUnit-format test reports with trends and per-test history.
- Install:
jenkins-plugin-cli --plugins junit
20. SonarQube Scanner
- Plugin ID:
sonar - What it does: Runs SonarQube analysis and can fail the pipeline when the quality gate fails, using
withSonarQubeEnvandwaitForQualityGate. - Install:
jenkins-plugin-cli --plugins sonar
21. Warnings Next Generation
- Plugin ID:
warnings-ng - What it does: Collects compiler warnings and static-analysis results (ESLint, Checkstyle, SpotBugs and more) into one report.
- Install:
jenkins-plugin-cli --plugins warnings-ng
22. JaCoCo / Coverage
- Plugin ID:
coverage(or the olderjacoco) - What it does: Shows code coverage and can fail builds below a threshold.
- Install:
jenkins-plugin-cli --plugins coverage
23. HTML Publisher
- Plugin ID:
htmlpublisher - What it does: Publishes HTML reports (test, coverage, Lighthouse) as links on the build page.
- Install:
jenkins-plugin-cli --plugins htmlpublisher
Notification Plugins
24. Slack Notification
- Plugin ID:
slack - What it does: Sends build results to Slack channels with
slackSend. - Install:
jenkins-plugin-cli --plugins slack
25. Email Extension
- Plugin ID:
email-ext - What it does: Configurable emails with templates, triggers and attachments, sent with
emailext. - Install:
jenkins-plugin-cli --plugins email-ext
26. Jira
- Plugin ID:
jira - What it does: Links builds to Jira issues mentioned in commits and can update issues from pipelines.
- Install:
jenkins-plugin-cli --plugins jira
Administration Plugins
27. Timestamper
- Plugin ID:
timestamper - What it does: Adds timestamps to console output so you can see which step is slow.
- Install:
jenkins-plugin-cli --plugins timestamper
28. Workspace Cleanup
- Plugin ID:
ws-cleanup - What it does: Deletes the workspace before or after a build with
cleanWs(), saving disk space and avoiding stale files. - Install:
jenkins-plugin-cli --plugins ws-cleanup
29. Build Timeout
- Plugin ID:
build-timeout - What it does: Stops stuck freestyle builds after a set time. (In pipelines use the built-in
timeoutstep.) - Install:
jenkins-plugin-cli --plugins build-timeout
30. Prometheus Metrics
- Plugin ID:
prometheus - What it does: Exposes Jenkins metrics (queue length, build durations, executor use) at
/prometheusfor Prometheus and Grafana. See Prometheus monitoring guide. - Install:
jenkins-plugin-cli --plugins prometheus
What Happened to Blue Ocean?
Blue Ocean was a popular redesigned UI for pipelines. It is no longer being developed, and the Jenkins documentation now recommends the Pipeline Graph View plugin (number 6 above) for pipeline visualisation, with Pipeline: Stage View as another option. Avoid installing Blue Ocean on new servers.
How to Install Jenkins Plugins

Method 1: Jenkins UI
- Go to Manage Jenkins → Plugins → Available plugins.
- Search for the plugin name.
- Tick it and click Install. Restart if Jenkins asks.
Method 2: jenkins-plugin-cli with plugins.txt (recommended)
Keep your plugin list in Git so every server is the same. plugins.txt takes one id:version per line:
workflow-aggregator:latest git:latest configuration-as-code:latest credentials-binding:latest docker-workflow:latest kubernetes:latest pipeline-graph-view:latest timestamper:latest slack:latest
Pin exact versions instead of latest for production. Then bake them into a custom image:
FROM jenkins/jenkins:lts-jdk21 COPY plugins.txt /usr/share/jenkins/ref/plugins.txt RUN jenkins-plugin-cli -f /usr/share/jenkins/ref/plugins.txt COPY casc.yaml /var/jenkins_home/casc.yaml ENV CASC_JENKINS_CONFIG=/var/jenkins_home/casc.yaml
Method 3: Upload an .hpi file
For air-gapped servers, download the .hpi file from plugins.jenkins.io, then go to Manage Jenkins → Plugins → Advanced settings → Deploy plugin and upload it. You must also upload its dependencies.
Configure Plugins with JCasC
Configuration as Code sets up plugins without clicking through the UI. A small casc.yaml:
jenkins:
systemMessage: "Configured by JCasC"
securityRealm:
local:
allowsSignup: false
authorizationStrategy:
roleBased:
roles:
global:
- name: admin
permissions: ["Overall/Administer"]
entries:
- group: "devops-admins"
unclassified:
slackNotifier:
teamDomain: paperlive
tokenCredentialId: slack-token
A Jenkinsfile That Uses These Plugins
This pipeline uses Pipeline, Git, Kubernetes, Docker Pipeline, Credentials Binding, SonarQube Scanner, JUnit, Timestamper, Workspace Cleanup and Slack together:
pipeline {
agent { kubernetes { inheritFrom 'docker-builder' } }
options { timestamps(); timeout(time: 30, unit: 'MINUTES') }
stages {
stage('Test') {
steps {
sh 'mvn -B test'
junit 'target/surefire-reports/*.xml'
}
}
stage('Code quality') {
steps {
withSonarQubeEnv('sonarqube') { sh 'mvn -B sonar:sonar' }
timeout(time: 5, unit: 'MINUTES') { waitForQualityGate abortPipeline: true }
}
}
stage('Image') {
steps {
script {
docker.withRegistry('https://ghcr.io', 'ghcr-creds') {
docker.build("paperlive/api:${env.GIT_COMMIT}").push()
}
}
}
}
}
post {
failure { slackSend channel: '#ci', color: 'danger', message: "Build failed: ${env.BUILD_URL}" }
cleanup { cleanWs() }
}
}
Jenkins Plugin Security Tips
- Check the plugin's health before installing: recent releases, open security warnings and the number of installs are shown on plugins.jenkins.io.
- Read security advisories: Jenkins shows warnings for vulnerable plugins in Manage Jenkins. Treat them as urgent.
- Avoid abandoned plugins: plugins marked "deprecated" or "up for adoption" may never get fixes.
- Limit who can install plugins: only administrators, and only through
plugins.txtreviews. - Prefer built-in features: for example the pipeline
timeoutstep instead of an extra plugin.
Managing and Updating Plugins
- Update plugins regularly; many updates are security fixes. Check Manage Jenkins → Plugins → Updates.
- Test upgrades on a staging Jenkins built from the same
plugins.txt. - Remove plugins you no longer use to cut risk and upgrade time.
- Back up
JENKINS_HOMEbefore big upgrades.
Getting ready for interviews too? Read Top 20 Jenkins interview questions and Jenkins vs GitHub Actions. Learn Jenkins with hands-on labs in our DevOps training.
Frequently Asked Questions
How do I install a Jenkins plugin from the command line?
Use jenkins-plugin-cli, which ships in the official Jenkins Docker image: jenkins-plugin-cli --plugins git:latest slack:latest. For a whole list, put one plugin per line in plugins.txt and run jenkins-plugin-cli -f plugins.txt.
Is Blue Ocean still supported?
Blue Ocean is no longer being developed. The Jenkins documentation recommends the Pipeline Graph View plugin for a modern pipeline visualisation, with Pipeline Stage View as another option.
How many plugins should a Jenkins server have?
As few as you need. Every plugin adds upgrade work and possible security issues. Keep a reviewed plugins.txt, remove unused plugins and update them regularly.
What is the most important Jenkins plugin?
The Pipeline plugin (workflow-aggregator), because it enables Jenkinsfile-based pipelines. Git and Credentials Binding are close behind.


