Plugin update management in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins CLI Plugin Update Check Output

You run the Jenkins CLI command to check for plugin updates:

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

What is the expected output if there are no plugin updates available?

A All plugins are up to date

B Error: No plugins found

C No plugins to update

D Update available for all plugins

💡 Hint

Think about the message Jenkins CLI shows when no updates exist.

The Jenkins CLI command list-plugins --updates outputs No plugins to update when all plugins are current.

❓ Configuration

intermediate

Configuring Automatic Plugin Updates in Jenkins

Which Jenkins configuration file is used to enable automatic plugin updates on startup?

A hudson.plugins.update-center.json

B hudson.plugins.update-center.xml

C jenkins.model.JenkinsLocationConfiguration.xml

D jenkins.yaml

💡 Hint

The file relates to the update center configuration.

The hudson.plugins.update-center.xml file configures plugin update settings including automatic updates.

🔀 Workflow

advanced

Safe Plugin Update Workflow in Jenkins

What is the recommended sequence to safely update Jenkins plugins without causing downtime?

A 3,1,2,4

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about what should be done before making changes.

Backing up first ensures recovery if updates fail. Checking compatibility avoids plugin conflicts. Then update plugins and restart Jenkins to apply changes.

❓ Troubleshoot

advanced

Troubleshooting Plugin Update Failure

After updating plugins, Jenkins fails to start and logs show java.lang.NoClassDefFoundError. What is the most likely cause?

A Plugin update caused version mismatch with Jenkins core

B Jenkins home directory is missing

C Network connectivity issue during update

D Incorrect Java version installed

💡 Hint

Consider what causes class definition errors after plugin updates.

NoClassDefFoundError usually means a plugin expects a different Jenkins core version than installed, causing incompatibility.

✅ Best Practice

expert

Best Practice for Managing Plugin Updates in Jenkins Pipelines

Which approach best ensures plugin updates do not break Jenkins pipelines in a production environment?

A Test plugin updates on a staging Jenkins instance before production rollout

B Disable all plugins and update Jenkins core only

C Update plugins directly on production Jenkins and monitor pipelines

D Schedule plugin updates during peak usage hours for faster feedback

💡 Hint

Think about minimizing risk to production pipelines.

Testing updates on a staging environment first prevents unexpected pipeline failures in production.