Plugin update management in Jenkins - Commands & Configuration

Introduction

Jenkins plugins add extra features to your Jenkins server. Keeping plugins updated fixes bugs and adds new features, making your server safer and more reliable.

When you want to add new capabilities to Jenkins like Git integration or pipeline support

When a plugin has a security update that protects your server

When a plugin update fixes bugs causing build failures

When you want to use new features introduced in the latest plugin versions

When you want to keep Jenkins stable by avoiding outdated plugins

Commands

This command lists all installed plugins on your Jenkins server with their current versions.

Terminal

java -jar jenkins-cli.jar -s http://localhost:8080/ list-plugins

Expected Output

ace-editor 1.1

ansicolor 0.7.0

git 4.10.0

pipeline 2.6

This command updates the 'git' and 'pipeline' plugins to their latest versions and deploys them immediately.

Terminal

java -jar jenkins-cli.jar -s http://localhost:8080/ install-plugin git pipeline -deploy

Expected Output

Installing plugin: git

Installing plugin: pipeline

Plugins installed successfully. Restart Jenkins to apply changes.

→

-deploy - Deploys the plugin immediately without waiting for a restart

This command restarts Jenkins safely to apply plugin updates without interrupting running jobs.

Terminal

java -jar jenkins-cli.jar -s http://localhost:8080/ safe-restart

Expected Output

Jenkins is restarting. Safe restart in progress...

After restart, this command verifies that plugins have been updated to the latest versions.

Terminal

java -jar jenkins-cli.jar -s http://localhost:8080/ list-plugins

Expected Output

ace-editor 1.1

ansicolor 0.7.0

git 4.11.0

pipeline 2.7

Key Concept

If you remember nothing else from this pattern, remember: always restart Jenkins safely after updating plugins to apply changes without breaking running jobs.

Common Mistakes

Updating plugins without restarting Jenkins

Plugin updates do not take effect until Jenkins restarts, so changes won't apply

Use 'safe-restart' command after plugin updates to apply changes properly

Updating plugins without checking compatibility

Some plugin updates may not be compatible with your Jenkins version causing failures

Check plugin compatibility on Jenkins update center before updating

Running plugin update commands without Jenkins CLI authentication

Commands fail because Jenkins requires authentication for CLI operations

Configure Jenkins CLI with proper authentication tokens or credentials

Summary

List installed plugins and their versions using Jenkins CLI.

Update specific plugins with the install-plugin command and deploy them.

Restart Jenkins safely to apply plugin updates without interrupting jobs.

Verify plugin versions after restart to confirm updates.

Practice

1. Why is it important to regularly update Jenkins plugins?

easy

A. To increase the Jenkins server's CPU speed

B. To change the Jenkins user interface color

C. To reduce the number of jobs in Jenkins

D. To keep Jenkins secure and stable

Solution

1. Step 1: Understand plugin role in Jenkins

   Plugins add features and fix bugs in Jenkins, affecting security and stability.

2. Step 2: Recognize update benefits

   Updating plugins patches vulnerabilities and improves performance, keeping Jenkins safe and reliable.

3. Final Answer:

   To keep Jenkins secure and stable -> Option D

4. Quick Check:

   Plugin updates = security and stability [OK]

Hint: Plugin updates fix bugs and security issues [OK]

Common Mistakes:

• Thinking updates speed up hardware
• Believing updates reduce job count
• Assuming updates change UI colors

2. Which command correctly lists all installed Jenkins plugins using the Jenkins Plugin CLI?

easy

A. jenkins-plugin-cli --list

B. jenkins-plugin-cli --plugins

C. jenkins-plugin-cli list-plugins

D. jenkins-plugin-cli --installed

Solution

1. Step 1: Recall Jenkins Plugin CLI syntax

   The correct command to list plugins is jenkins-plugin-cli list-plugins.

2. Step 2: Verify other options

   Options like --list, --plugins, or --installed are not valid commands.

3. Final Answer:

   jenkins-plugin-cli list-plugins -> Option C

4. Quick Check:

   List plugins = list-plugins [OK]

Hint: Use list-plugins command to show plugins [OK]

Common Mistakes:

• Using incorrect flags like --plugins
• Typing commands not supported by CLI
• Confusing list with install commands

3. What will be the output of the command jenkins-plugin-cli --upgrade if all plugins are already up to date?

medium

A. No plugins to upgrade

B. Upgrade failed due to network error

C. Error: No plugins found

D. All plugins upgraded successfully

Solution

1. Step 1: Understand the upgrade command behavior

   The --upgrade command checks for plugin updates and upgrades if available.

2. Step 2: Consider the case when no updates exist

   If all plugins are current, the CLI reports no plugins need upgrading.

3. Final Answer:

   No plugins to upgrade -> Option A

4. Quick Check:

   All plugins current = no upgrade needed [OK]

Hint: If no updates, CLI says no plugins to upgrade [OK]

Common Mistakes:

• Assuming it always says upgrade success
• Expecting error when no updates
• Confusing network errors with normal output

4. You ran jenkins-plugin-cli --upgrade but some plugins failed to update. What is a common cause and fix?

medium

A. Plugin syntax error; edit plugin files manually

B. Network issues; check internet connection and retry

C. Jenkins version too new; downgrade Jenkins

D. Disk full; uninstall Jenkins

Solution

1. Step 1: Identify common upgrade failure reasons

   Network problems often cause plugin download failures during upgrade.

2. Step 2: Apply the fix

   Check and fix internet connection, then retry the upgrade command.

3. Final Answer:

   Network issues; check internet connection and retry -> Option B

4. Quick Check:

   Upgrade fail = network check [OK]

Hint: Check network if plugin upgrade fails [OK]

Common Mistakes:

• Editing plugin files manually
• Downgrading Jenkins unnecessarily
• Uninstalling Jenkins to fix disk issues

5. Before updating Jenkins plugins, what is the best practice to avoid breaking your Jenkins setup?

hard

A. Backup Jenkins data and verify plugin compatibility

B. Delete all old plugins to start fresh

C. Update Jenkins core first without plugins

D. Restart Jenkins server multiple times

Solution

1. Step 1: Understand risks of plugin updates

   Plugin updates can cause incompatibility or data loss if not prepared properly.

2. Step 2: Identify safe update steps

   Backing up Jenkins data and checking plugin compatibility prevents breakage during updates.

3. Final Answer:

   Backup Jenkins data and verify plugin compatibility -> Option A

4. Quick Check:

   Backup + compatibility check = safe updates [OK]

Hint: Always backup and check compatibility before updates [OK]

Common Mistakes:

• Deleting plugins unnecessarily
• Updating core without plugin checks
• Restarting server without backup