Plugins and Extensions

Plugins and Extensions

Plugins provide source-control integrations, credentials providers, agents, pipeline steps, reports, authentication, and UI features. This extensibility is powerful, but plugins execute inside Jenkins and form part of its security and availability boundary.

Core ideas

• Plugins can depend on other plugins and minimum Jenkins core versions.
• The update center publishes metadata and available versions; production access may use an internal mirror.
• A disabled plugin remains installed but inactive; uninstalling may leave configuration that referenced it.
• A plugin bill of materials and configuration backup make incidents and upgrades easier to manage.

How it works

Begin with the smallest supported plugin set. Record purpose and owner, review health and security notices, and remove abandoned dependencies. Upgrade in a test controller using a copy of representative configuration, then validate authentication, agents, critical pipelines, and rollback.

Configuration example

# List installed plugins with versions via Jenkins CLI
java -jar jenkins-cli.jar -s https://jenkins.example.com/ \
  -auth "$JENKINS_USER:$JENKINS_TOKEN" list-plugins

# Compare this inventory with an approved, version-controlled baseline

The sample is intentionally small. In a real installation, replace hostnames, labels, credentials, retention, and commands with reviewed values from your own platform standards.

Production guidance

• Do not install plugins directly in production merely to experiment.
• Back up before upgrades and preserve a compatible core/plugin rollback plan.
• Prefer built-in Pipeline capabilities or maintained plugins over overlapping extensions with unclear ownership.

The chapter quiz follows this lesson and tests both terminology and safe operating choices.