Plugin manager usage in Jenkins - Mini Project: Build & Apply

Plugin manager usage

📖 Scenario: You are setting up a Jenkins server for your team. To add new features, you need to manage Jenkins plugins using the Plugin Manager.

🎯 Goal: Learn how to list installed plugins, install a new plugin, and verify the installation using Jenkins Plugin Manager commands.

📋 What You'll Learn

Use Jenkins CLI commands to interact with the Plugin Manager

List currently installed plugins

Install a specific plugin by name

Verify the plugin installation

💡 Why This Matters

🌍 Real World

Managing Jenkins plugins is essential for adding new features and integrations to your CI/CD pipelines.

💼 Career

Knowing how to use Jenkins Plugin Manager commands is a key skill for DevOps engineers and system administrators managing Jenkins servers.

1

List installed plugins

Use the Jenkins CLI command java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins to list all currently installed plugins.

Jenkins

# Run the command to list installed plugins
# Your code here

Hint

This command connects to your Jenkins server and shows all plugins installed.

2

Install a new plugin

Use the Jenkins CLI command java -jar jenkins-cli.jar -s http://localhost:8080 install-plugin git to install the git plugin.

Jenkins

java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins
# Run the command to install the git plugin
# Your code here

Hint

This command installs the git plugin on your Jenkins server.

3

Restart Jenkins to apply changes

Use the Jenkins CLI command java -jar jenkins-cli.jar -s http://localhost:8080 safe-restart to safely restart Jenkins and apply the plugin installation.

Jenkins

java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins
java -jar jenkins-cli.jar -s http://localhost:8080 install-plugin git
# Run the command to safely restart Jenkins
# Your code here

Hint

Restart Jenkins safely so the new plugin is loaded without interrupting running jobs.

4

Verify the git plugin installation

Run java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins | grep git to check if the git plugin is installed and active.

Jenkins

java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins
java -jar jenkins-cli.jar -s http://localhost:8080 install-plugin git
java -jar jenkins-cli.jar -s http://localhost:8080 safe-restart
# Run the command to verify git plugin installation
# Your code here

Hint

This command filters the plugin list to show only the git plugin, confirming it is installed.

Practice

1. What is the primary purpose of the Jenkins Plugin Manager?

easy

A. To monitor Jenkins build logs

B. To add, update, or remove Jenkins plugins easily

C. To create new Jenkins jobs

D. To configure Jenkins system settings

Solution

1. Step 1: Understand Jenkins Plugin Manager role

   The Plugin Manager is designed to handle plugins, which extend Jenkins features.

2. Step 2: Differentiate from other Jenkins functions

   Configuring system settings, creating jobs, and monitoring logs are separate Jenkins tasks, not plugin management.

3. Final Answer:

   To add, update, or remove Jenkins plugins easily -> Option B

4. Quick Check:

   Plugin Manager = Manage plugins [OK]

Hint: Plugin Manager is for plugins only, not jobs or settings [OK]

Common Mistakes:

• Confusing plugin management with job creation
• Thinking it manages Jenkins system settings
• Assuming it monitors build logs

2. Which menu path in Jenkins web interface leads you to the Plugin Manager?

easy

A. Manage Jenkins > Manage Plugins

B. Dashboard > New Item

C. Build History > Configure

D. Manage Jenkins > System Log

Solution

1. Step 1: Locate Plugin Manager in Jenkins UI

   The Plugin Manager is accessed via 'Manage Jenkins' then 'Manage Plugins'.

2. Step 2: Eliminate incorrect paths

   'New Item' creates jobs, 'Configure' edits builds, 'System Log' shows logs, none manage plugins.

3. Final Answer:

   Manage Jenkins > Manage Plugins -> Option A

4. Quick Check:

   Plugin Manager location = Manage Jenkins > Manage Plugins [OK]

Hint: Plugin Manager is always under Manage Jenkins > Manage Plugins [OK]

Common Mistakes:

• Selecting Dashboard > New Item by mistake
• Confusing System Log with Plugin Manager
• Choosing Build History > Configure incorrectly

3. After selecting a plugin to install in Jenkins Plugin Manager, what happens if you choose 'Install without restart'?

medium

A. The plugin downloads but requires a manual restart to activate

B. The plugin installation fails until Jenkins is restarted

C. The plugin installation is scheduled for the next Jenkins restart automatically

D. The plugin installs immediately and is usable without restarting Jenkins

Solution

1. Step 1: Understand 'Install without restart' option

   This option installs the plugin immediately and activates it without needing a restart.

2. Step 2: Compare with other options

   Other options either delay activation until restart or require manual restart; installation does not fail automatically.

3. Final Answer:

   The plugin installs immediately and is usable without restarting Jenkins -> Option D

4. Quick Check:

   Install without restart = immediate use [OK]

Hint: Install without restart means plugin is ready immediately [OK]

Common Mistakes:

• Assuming plugin needs restart to activate
• Thinking installation is scheduled for later
• Believing installation fails without restart

4. You tried to install a plugin but it did not appear in the installed list after installation. What is the most likely cause?

medium

A. You installed the plugin from the wrong Jenkins menu

B. You installed the plugin without internet connection

C. You selected 'Download now and install after restart' but did not restart Jenkins

D. The plugin is incompatible with your Jenkins version

Solution

1. Step 1: Analyze installation options

   If 'Download now and install after restart' is chosen, plugin activates only after Jenkins restarts.

2. Step 2: Check other causes

   Installing without internet would fail download; wrong menu prevents installation; incompatibility usually shows error.

3. Final Answer:

   You selected 'Download now and install after restart' but did not restart Jenkins -> Option C

4. Quick Check:

   Plugin visible after restart only if delayed install chosen [OK]

Hint: Restart Jenkins if plugin installed with delayed option [OK]

Common Mistakes:

• Not restarting Jenkins after delayed install
• Ignoring internet connection issues
• Confusing menu locations for plugin install

5. You want to update multiple plugins at once using Jenkins Plugin Manager. Which approach is best to ensure minimal downtime?

hard

A. Select all plugins and choose 'Download now and install after restart', then restart Jenkins once

B. Update each plugin one by one with 'Install without restart' option

C. Uninstall all plugins first, then install latest versions separately

D. Restart Jenkins before updating plugins to clear cache

Solution

1. Step 1: Consider updating multiple plugins efficiently

   Choosing 'Download now and install after restart' for all plugins allows batch update with a single restart.

2. Step 2: Evaluate other options

   Updating one by one without restart may cause instability; uninstalling first is unnecessary; restarting before update doesn't help.

3. Final Answer:

   Select all plugins and choose 'Download now and install after restart', then restart Jenkins once -> Option A

4. Quick Check:

   Batch update with one restart = minimal downtime [OK]

Hint: Batch update plugins, restart once after all downloads [OK]

Common Mistakes:

• Updating plugins one by one causing multiple restarts
• Uninstalling plugins unnecessarily
• Restarting Jenkins before updates without need