Opscraft
Jenkins · Lesson 4 of 11 · 3 min read

Plugins and their management

Plugins you should be able to name

Area Plugins
Pipeline core Pipeline (workflow-aggregator), Pipeline: Declarative, Pipeline Stage View, Blue Ocean (visual UI, now in maintenance), Pipeline Graph View
SCM Git, GitHub Branch Source, Bitbucket Branch Source, GitLab
Agents Kubernetes, Docker Pipeline, EC2, SSH Build Agents
Credentials Credentials, Credentials Binding, Plain Credentials, AWS Credentials, HashiCorp Vault
Security Role-based Authorization Strategy, Matrix Authorization, OIDC/SAML/LDAP/Active Directory
As-code Configuration as Code (JCasC), Job DSL, Pipeline: Shared Groovy Libraries
Quality JUnit, JaCoCo, Warnings Next Generation, SonarQube Scanner
Utilities Pipeline Utility Steps (readYaml/readJSON), Timestamper, Workspace Cleanup, Lockable Resources, Throttle Concurrent Builds, Slack Notification, Email Extension

Plugin management done properly

Plugins are Jenkins' strength and its biggest operational risk: dependency chains, breaking upgrades, abandoned plugins, and most Jenkins security advisories.

  • Pin plugin versions in a plugins.txt and bake them into a custom controller image with jenkins-plugin-cli:
FROM jenkins/jenkins:2.479.1-lts-jdk21
COPY plugins.txt /usr/share/jenkins/ref/plugins.txt
RUN jenkins-plugin-cli --plugin-file /usr/share/jenkins/ref/plugins.txt
COPY casc/ /var/jenkins_home/casc_configs/
ENV CASC_JENKINS_CONFIG=/var/jenkins_home/casc_configs
  • Minimise plugins — each one is attack surface and upgrade risk. Remove unused ones.
  • Prefer plugins that are actively maintained (check the plugin site for last release and open security warnings).
  • Upgrade core (LTS) and plugins together, tested on a staging controller first.
  • Jenkins shows security warnings in the UI for plugins with published vulnerabilities — treat them like CVEs.
Enlarge diagramClick-opsPinned imageInstall and upgrade in the UIVersions drift, nobody knows whichOne bad upgrade, no way backplugins.txt in Gitjenkins-plugin-cli in the DockerfileRoll back by redeploying the old image
Figure 1. Plugins done properly: pinned in a file, baked into an image, tested before production. Never click-install on the live controller.
Swipe sideways to see all of it, or tap to open it full screen.