Installing suggested plugins in Jenkins - Step-by-Step CLI Walkthrough

Introduction

When you first set up Jenkins, it offers to install suggested plugins. These plugins add useful features to Jenkins without you needing to find and install each one manually.

When you install Jenkins for the first time and want a ready-to-use setup.

When you want to quickly add common tools like Git, pipeline support, and build triggers.

When you prefer Jenkins to handle plugin selection instead of choosing manually.

When setting up a Jenkins server for a team that needs standard CI/CD features.

When you want to avoid missing important plugins that Jenkins recommends.

Commands

This command starts the Jenkins service so you can access the web interface to install plugins.

Terminal

sudo systemctl start jenkins

Expected Output

No output (command runs silently)

This command checks if Jenkins is running by requesting the homepage on port 8080.

Terminal

curl http://localhost:8080

Expected Output

<!DOCTYPE html>

<html lang="en">

<head><title>Unlock Jenkins</title></head>

<body>Unlock Jenkins page content</body>

</html>

This step represents using the Jenkins web interface to select 'Install suggested plugins'. This cannot be done via CLI but is essential to complete the setup.

Terminal

echo 'Installing suggested plugins via Jenkins web UI'

Expected Output

Installing suggested plugins via Jenkins web UI

This command follows the Jenkins logs to watch the plugin installation progress and verify no errors occur.

Terminal

sudo journalctl -u jenkins -f

Expected Output

Apr 27 12:00:00 jenkins-server jenkins[1234]: Started installing suggested plugins...

Apr 27 12:01:30 jenkins-server jenkins[1234]: Plugin installation completed successfully.

→

-u jenkins - Show logs only for the Jenkins service

→

-f - Follow the log output live

Key Concept

If you remember nothing else from this pattern, remember: installing suggested plugins via the Jenkins web UI quickly sets up essential features for your Jenkins server.

Common Mistakes

Trying to install suggested plugins using only CLI commands without using the Jenkins web interface.

Jenkins does not support installing suggested plugins purely via CLI during initial setup.

Access the Jenkins web UI on port 8080 and choose 'Install suggested plugins' to proceed.

Not starting the Jenkins service before accessing the web interface.

If Jenkins is not running, the web interface will be unreachable and plugin installation cannot start.

Start Jenkins service with 'sudo systemctl start jenkins' before opening the web UI.

Summary

Start the Jenkins service to make the web interface available.

Access Jenkins on port 8080 and select 'Install suggested plugins' in the web UI.

Monitor Jenkins logs to confirm plugins install successfully.

Practice

1. What does the Installing suggested plugins option do during Jenkins setup?

easy

A. It removes all existing plugins from Jenkins.

B. It adds useful features automatically to Jenkins after installation.

C. It disables Jenkins security settings.

D. It resets Jenkins to factory defaults.

Solution

1. Step 1: Understand the purpose of suggested plugins

   Suggested plugins provide common features that most Jenkins users need right after setup.

2. Step 2: Recognize the effect of installing suggested plugins

   Installing them adds these features automatically, saving manual installation later.

3. Final Answer:

   It adds useful features automatically to Jenkins after installation. -> Option B

4. Quick Check:

   Suggested plugins = add useful features [OK]

Hint: Suggested plugins add common features automatically [OK]

Common Mistakes:

• Thinking it removes plugins
• Confusing with security settings
• Assuming it resets Jenkins

2. Which option correctly describes the Jenkins setup wizard step for installing suggested plugins?

easy

A. It appears automatically during the initial setup wizard.

B. It appears only if you manually enable it in settings.

C. It is hidden and requires command line to access.

D. It is available only after Jenkins is fully configured.

Solution

1. Step 1: Recall Jenkins setup wizard behavior

   The setup wizard shows the option to install suggested plugins automatically during initial setup.

2. Step 2: Confirm when the option appears

   This option is visible by default and does not require manual enabling or command line.

3. Final Answer:

   It appears automatically during the initial setup wizard. -> Option A

4. Quick Check:

   Setup wizard shows suggested plugins option automatically [OK]

Hint: Suggested plugins option shows up automatically in setup [OK]

Common Mistakes:

• Thinking it needs manual enabling
• Believing it is command line only
• Assuming it appears after full setup

3. After skipping the suggested plugins installation during Jenkins setup, what is the correct way to add them later?

medium

A. Use the Jenkins Plugin Manager to install plugins manually.

B. Re-run the setup wizard to reinstall suggested plugins.

C. Edit Jenkins configuration files to add plugins.

D. Restart Jenkins with a special flag to auto-install plugins.

Solution

1. Step 1: Understand plugin management in Jenkins

   Jenkins provides a Plugin Manager UI to install, update, or remove plugins anytime.

2. Step 2: Identify how to add suggested plugins after setup

   If skipped during setup, you can manually install suggested plugins via the Plugin Manager.

3. Final Answer:

   Use the Jenkins Plugin Manager to install plugins manually. -> Option A

4. Quick Check:

   Manual plugin install = Plugin Manager [OK]

Hint: Use Plugin Manager to add plugins after setup [OK]

Common Mistakes:

• Trying to rerun setup wizard
• Editing config files directly
• Using restart flags to install plugins

4. You skipped installing suggested plugins during Jenkins setup but now see missing features. What is the best way to fix this?

medium

A. Ignore the missing features; they cannot be added later.

B. Delete Jenkins and reinstall it to get suggested plugins.

C. Manually install the missing plugins using the Plugin Manager.

D. Run a shell script to force install all plugins automatically.

Solution

1. Step 1: Identify the cause of missing features

   Skipping suggested plugins means those features are not installed yet.

2. Step 2: Choose the proper fix method

   The Plugin Manager allows manual installation of any missing plugins without reinstalling Jenkins.

3. Final Answer:

   Manually install the missing plugins using the Plugin Manager. -> Option C

4. Quick Check:

   Fix missing features = Plugin Manager install [OK]

Hint: Use Plugin Manager to fix missing plugins, no reinstall needed [OK]

Common Mistakes:

• Reinstalling Jenkins unnecessarily
• Assuming missing features can't be added
• Using unsafe scripts to force install

5. You want to automate Jenkins setup including installing suggested plugins on multiple servers. Which approach is best?

hard

A. Skip plugins during setup and install them later one by one manually.

B. Manually install Jenkins and plugins on each server using the web UI.

C. Run Jenkins setup wizard interactively on each server.

D. Use Jenkins Configuration as Code (JCasC) plugin to define plugins in YAML and apply during setup.

Solution

1. Step 1: Understand automation needs for multiple servers

   Manual or interactive setup is slow and error-prone for many servers.

2. Step 2: Identify Jenkins automation tools

   Jenkins Configuration as Code (JCasC) allows defining plugins and settings in YAML files for automated setup.

3. Step 3: Apply JCasC for installing suggested plugins

   By listing plugins in JCasC YAML, Jenkins installs them automatically on startup without manual steps.

4. Final Answer:

   Use Jenkins Configuration as Code (JCasC) plugin to define plugins in YAML and apply during setup. -> Option D

5. Quick Check:

   Automate plugin install = JCasC YAML config [OK]

Hint: Automate plugin install with JCasC YAML config [OK]

Common Mistakes:

• Doing manual installs on each server
• Skipping plugins then installing manually
• Running interactive setup repeatedly