Plugin update management in Jenkins - Step-by-Step Execution

Process Flow - Plugin update management

Check for plugin updates

↓

List available updates

↓

Select plugins to update

↓

Download updates

↓

Install updates

↓

Restart Jenkins if needed

↓

Done

This flow shows how Jenkins checks for plugin updates, downloads, installs them, and restarts if required.

Execution Sample

Jenkins

java -jar jenkins-cli.jar -s http://localhost:8080/ list-plugins --updates
java -jar jenkins-cli.jar -s http://localhost:8080/ install-plugin plugin-name
java -jar jenkins-cli.jar -s http://localhost:8080/ safe-restart

These commands check for plugin updates, install a plugin update, and safely restart Jenkins.

Process Table

Step	Action	Command	Result	Notes
1	Check for updates	list-plugins --updates	Shows plugins with available updates	Lists plugins that can be updated
2	Select plugin	install-plugin plugin-name	Downloads and installs plugin update	Plugin updated on Jenkins server
3	Restart Jenkins	safe-restart	Jenkins restarts safely	Applies plugin updates fully
4	Verify update	list-plugins	Shows updated plugin version	Confirms update success

💡 All selected plugins updated and Jenkins restarted to apply changes

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
AvailableUpdates	[]	[pluginA v1.0 -> v1.1]	[pluginA v1.1 installed]	[Jenkins restarted]	[pluginA v1.1 active]

Key Moments - 2 Insights

Why do we need to restart Jenkins after plugin updates?

Restarting Jenkins applies the new plugin versions fully. Without restart, old plugin code may still run. See execution_table step 3 where 'safe-restart' is used.

What happens if we try to install a plugin update without checking for updates first?

You might install an outdated or wrong version. Checking updates first (step 1) ensures you install the latest available plugin version.

Visual Quiz - 3 Questions

Look at the execution table, what command lists plugins with available updates?

A install-plugin plugin-name

B list-plugins --updates

C safe-restart

D list-plugins

💡 Hint

Check Step 1 in the execution_table under Command column

At which step does Jenkins restart to apply plugin updates?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at Step 3 in execution_table where 'safe-restart' is run

If you skip the restart step, what is the likely outcome?

A Plugin updates apply immediately

B Jenkins crashes

C Old plugin versions keep running

D Plugins uninstall automatically

💡 Hint

Refer to key_moments about why restart is needed after updates

Concept Snapshot

Jenkins plugin update management:
1. Check for updates with 'list-plugins --updates'
2. Install updates using 'install-plugin plugin-name'
3. Restart Jenkins safely with 'safe-restart' to apply changes
4. Verify updated plugins with 'list-plugins'
Always restart Jenkins to activate new plugin versions.

Full Transcript

This visual execution shows how Jenkins manages plugin updates step-by-step. First, Jenkins checks for available plugin updates using the 'list-plugins --updates' command. Then, you select and install the desired plugin updates with 'install-plugin plugin-name'. After installation, Jenkins must be restarted safely using 'safe-restart' to fully apply the new plugin versions. Finally, you verify the updates by listing plugins again. Restarting Jenkins is crucial because without it, old plugin code may still run, preventing updates from taking effect. Skipping the restart step means the plugins won't update properly. This process ensures your Jenkins server stays current and stable with the latest plugin features and fixes.