Why plugins extend Jenkins - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to install a plugin in Jenkins using the CLI.

Jenkins

java -jar jenkins-cli.jar -s http://localhost:8080 install-plugin [1]

Drag options to blanks, or click blank then click option'

Agit

Bdocker

Cnodejs

Dmaven

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a plugin unrelated to source control.

The git plugin is a common plugin to extend Jenkins for Git repository support.

2fill in blank

medium

Complete the code to restart Jenkins after installing a plugin.

Jenkins

java -jar jenkins-cli.jar -s http://localhost:8080 [1]

Drag options to blanks, or click blank then click option'

Arestart-now

Breload-configuration

Csafe-restart

Dshutdown

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'shutdown' which stops Jenkins without restart.

The safe-restart command restarts Jenkins safely after plugin installation.

3fill in blank

hard

Fix the error in the plugin installation command by choosing the correct option.

Jenkins

java -jar jenkins-cli.jar -s http://localhost:8080 install-plugin [1] --deploy

Drag options to blanks, or click blank then click option'

A--plugin

Bgit

C--install

Ddocker

Attempts:

3 left

💡 Hint

Common Mistakes

Adding extra flags before the plugin name.

The plugin name git should be specified directly without extra flags.

4fill in blank

hard

Fill both blanks to create a Jenkins pipeline step that uses a plugin to build a Docker image.

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        [1] '[2]'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Adocker.build

Bsh

Cmy-image:latest

Decho

Attempts:

3 left

💡 Hint

Common Mistakes

Using shell commands instead of the docker plugin step.

The docker.build step builds a Docker image named my-image:latest.

5fill in blank

hard

Fill all three blanks to define a Jenkins pipeline that uses the Git plugin to clone a repository and then runs a shell command.

Jenkins

pipeline {
  agent any
  stages {
    stage('Checkout') {
      steps {
        [1] '[2]'
      }
    }
    stage('Build') {
      steps {
        [3] 'make build'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Agit

Bhttps://github.com/example/repo.git

Csh

Dcheckout

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'checkout' instead of 'git' for cloning.

The git step clones the repository URL, and sh runs the shell command.

Practice

1. Why do Jenkins plugins exist?

easy

A. To add new features without changing Jenkins core

B. To replace Jenkins core completely

C. To slow down Jenkins builds

D. To remove existing Jenkins features

Solution

1. Step 1: Understand Jenkins core stability

   Jenkins core is stable and plugins add extra features without changing it.

2. Step 2: Recognize plugin purpose

   Plugins extend Jenkins by adding new tools and build steps, not replacing or removing features.

3. Final Answer:

   To add new features without changing Jenkins core -> Option A

4. Quick Check:

   Plugins extend Jenkins = To add new features without changing Jenkins core [OK]

Hint: Plugins add features, they don't replace core [OK]

Common Mistakes:

• Thinking plugins replace Jenkins core
• Believing plugins slow down Jenkins intentionally
• Assuming plugins remove features

2. Which of these is the correct way to install a Jenkins plugin via the UI?

easy

A. Edit Jenkinsfile and add plugin name

B. Go to Manage Jenkins > Manage Plugins > Available tab > Select plugin > Install

C. Run 'jenkins install plugin' command in terminal

D. Restart Jenkins without any action

Solution

1. Step 1: Locate plugin installation in Jenkins UI

   Plugins are installed via Manage Jenkins > Manage Plugins > Available tab.

2. Step 2: Understand installation process

   Select the desired plugin and click Install to add it.

3. Final Answer:

   Go to Manage Jenkins > Manage Plugins > Available tab > Select plugin > Install -> Option B

4. Quick Check:

   UI plugin install = Go to Manage Jenkins > Manage Plugins > Available tab > Select plugin > Install [OK]

Hint: Use Manage Plugins in Jenkins UI to install plugins [OK]

Common Mistakes:

• Trying to install plugins by editing Jenkinsfile
• Using wrong terminal commands
• Restarting Jenkins without installing plugins

3. What will happen if you try to use a plugin feature in Jenkins without installing the plugin first?

medium

A. Jenkins will show an error or not recognize the feature

B. Jenkins will automatically install the plugin

C. The feature will work without any issue

D. Jenkins will disable all plugins

Solution

1. Step 1: Understand plugin dependency

   Plugin features require the plugin to be installed to work properly.

2. Step 2: Predict Jenkins behavior without plugin

   Without the plugin, Jenkins cannot recognize or run the feature, causing errors.

3. Final Answer:

   Jenkins will show an error or not recognize the feature -> Option A

4. Quick Check:

   Missing plugin = error or unknown feature [OK]

Hint: Missing plugin means feature won't work, expect error [OK]

Common Mistakes:

• Assuming Jenkins auto-installs missing plugins
• Thinking features work without plugins
• Believing Jenkins disables all plugins on error

4. You installed a plugin but Jenkins does not show its features. What should you check first?

medium

A. If Jenkins core version is below 1.0

B. If the plugin was uninstalled

C. If Jenkinsfile contains the plugin name

D. If Jenkins was restarted after plugin installation

Solution

1. Step 1: Confirm plugin installation

   Plugin must be installed and Jenkins restarted to activate new features.

2. Step 2: Identify common issue

   Not restarting Jenkins after plugin install often causes features not to appear.

3. Final Answer:

   If Jenkins was restarted after plugin installation -> Option D

4. Quick Check:

   Restart Jenkins after plugin install = If Jenkins was restarted after plugin installation [OK]

Hint: Always restart Jenkins after installing plugins [OK]

Common Mistakes:

• Ignoring Jenkins restart after plugin install
• Checking Jenkinsfile instead of Jenkins UI
• Assuming old Jenkins core version is the cause

5. You want Jenkins to send notifications to Slack after builds. Which approach best uses plugins to achieve this?

hard

A. Modify Jenkins core files to add Slack support

B. Write a custom script in Jenkinsfile without any plugin

C. Install the Slack Notification plugin and configure it in Jenkins settings

D. Use Jenkins without plugins and send emails instead

Solution

1. Step 1: Identify plugin for Slack notifications

   The Slack Notification plugin adds Slack support without changing Jenkins core.

2. Step 2: Configure plugin properly

   After installing, configure Slack details in Jenkins to enable notifications.

3. Final Answer:

   Install the Slack Notification plugin and configure it in Jenkins settings -> Option C

4. Quick Check:

   Use Slack plugin for notifications = Install the Slack Notification plugin and configure it in Jenkins settings [OK]

Hint: Use official plugins for tool integration like Slack [OK]

Common Mistakes:

• Trying to modify Jenkins core files
• Skipping plugins and writing complex scripts
• Ignoring plugin configuration after install