---
id: cd91027c-a568-4e9a-9bf5-4c76a189664b
---

# Jenkins Outdated Plugins Incident
---

The Jenkins outdated plugins incident occurs when one or more plugins installed on a Jenkins server are not up to date. This can lead to potential security vulnerabilities, performance issues, and compatibility problems with other plugins or applications that rely on them. The incident requires immediate attention and updates to the affected plugins to ensure the smooth functioning of Jenkins and prevent any potential security threats.

### Parameters
```shell
export JENKINS_HOME="PLACEHOLDER"

export YOUR_JENKINS_PASSWORD="PLACEHOLDER"

export YOUR_JENKINS_USERNAME="PLACEHOLDER"

export LIST_OF_PLUGINS_TO_UPDATE="PLACEHOLDER"

export YOUR_JENKINS_URL="PLACEHOLDER"

export PATH_TO_JENKINS_UPDATE_CENTER="PLACEHOLDER"

export PATH_TO_JENKINS_PLUGINS="PLACEHOLDER"
```

## Debug

### Check the version of Jenkins running.
```shell
${JENKINS_HOME}/jenkins.sh version
```

### List all installed plugins along with their versions.
```shell
${JENKINS_HOME}/jenkins.sh list-plugins
```

### Check if any plugins have updates available.
```shell
${JENKINS_HOME}/jenkins.sh list-plugins | grep -v ')$' | awk '{ print $1 }' | xargs ${JENKINS_HOME}/jenkins.sh install-plugin
```

### Verify the status of updated plugins.
```shell
${JENKINS_HOME}/jenkins.sh list-plugins | grep -v ')$'
```

### Restart Jenkins for changes to take effect.
```shell
${JENKINS_HOME}/jenkins.sh restart
```

### The system administrator may have overlooked plugin update notifications and failed to update them in a timely manner.
```shell


#!/bin/bash



# Set the path to the Jenkins plugins directory

PLUGINS_DIR=${PATH_TO_JENKINS_PLUGINS}



# Get a list of all installed plugins

INSTALLED_PLUGINS=$(ls $PLUGINS_DIR)



# Set the path to the Jenkins update center

UPDATE_CENTER=${PATH_TO_JENKINS_UPDATE_CENTER}



# Get a list of all available plugin updates from the update center

AVAILABLE_UPDATES=$(curl $UPDATE_CENTER/update-center.json | grep -o '\"name\": \"[^\"]*\"' | awk -F ':' '{print $2}' | sed 's/\"//g')



# Check if any installed plugins have available updates

for plugin in $INSTALLED_PLUGINS; do

  if [[ $AVAILABLE_UPDATES =~ $plugin ]]; then

    echo "Plugin '$plugin' has an available update."

  fi

done


```

## Repair

### During the maintenance window, update the plugins by either manually downloading them from the Jenkins update center or by using a plugin manager tool like Jenkins CLI or Jenkins Configuration as Code.
```shell


#!/bin/bash



# Define variables

JENKINS_URL="${YOUR_JENKINS_URL}"

JENKINS_USERNAME="${YOUR_JENKINS_USERNAME}"

JENKINS_PASSWORD="${YOUR_JENKINS_PASSWORD}"

PLUGINS="${LIST_OF_PLUGINS_TO_UPDATE}"



# Download Jenkins CLI

wget "${JENKINS_URL}/jnlpJars/jenkins-cli.jar"



# Install plugins using Jenkins CLI

java -jar jenkins-cli.jar -s "${JENKINS_URL}" -auth "${JENKINS_USERNAME}:${JENKINS_PASSWORD}" install-plugin ${PLUGINS}



# Restart Jenkins to apply the changes

java -jar jenkins-cli.jar -s "${JENKINS_URL}" -auth "${JENKINS_USERNAME}:${JENKINS_PASSWORD}" restart


```

The Jenkins outdated plugins incident occurs when one or more plugins installed on a Jenkins server are not up to date. This can lead to potential security vulnerabilities, performance issues, and compatibility problems with other plugins or applications that rely on them. The incident requires immediate attention and updates to the affected plugins to ensure the smooth functioning of Jenkins and prevent any potential security threats.


Tomcat Server Crash incident type refers to a situation where the Tomcat Server, an open-source web server and servlet container, becomes unresponsive and stops functioning. This can result in a complete or partial system outage, leading to a disruption in the delivery of web applications and services. The root cause of the crash can be attributed to a variety of factors such as misconfiguration, network or hardware issues, software bugs, or excessive server load. It is critical to address this incident quickly to minimize the impact on users and restore normal system functionality.


Tomcat Server Crash

This incident type usually occurs when there is a failure in the SSL Handshake process between a client and server running on a Tomcat web server. This can happen for various reasons such as incorrect SSL certificate configuration, cipher suite mismatches, or network connectivity issues. When this type of incident is not resolved quickly, it can lead to downtime or service disruptions for users trying to access the affected service.


Tomcat SSL Handshake Failure Incident

Tomcat JVM OutOfMemory incident occurs when the Java Virtual Machine (JVM) running the Apache Tomcat server runs out of memory, which causes the server to crash or become unresponsive. This type of incident can happen due to a variety of reasons such as incorrect configuration settings, memory leaks, or insufficient memory allocation. When this incident occurs, it can impact the availability and performance of the web application running on the Tomcat server.


Tomcat JVM OutOfMemory Incident

This incident type refers to a failure in one or more Spark executors during the execution of a job. Spark executors are worker processes that run computations and store data in memory or on disk. When an executor fails, it can cause the entire job to fail or result in degraded performance. This type of incident can occur for a variety of reasons, such as hardware or network issues, memory errors, or software bugs.


Spark executor failure during job execution.

Apache Spark Out of Memory Error is a type of incident that occurs when the Apache Spark application running on a system is unable to allocate enough memory to perform its tasks. This can happen when the system's memory is insufficient or when there is a memory leak in the application's code. When this incident occurs, the application may crash, become unresponsive, or produce incorrect results. It is important to diagnose and resolve this issue as soon as possible to ensure the smooth functioning of the application.


Apache Spark Out of Memory Error incident.

```shell
export JENKINS_HOME="PLACEHOLDER"

export YOUR_JENKINS_PASSWORD="PLACEHOLDER"

export YOUR_JENKINS_USERNAME="PLACEHOLDER"

export LIST_OF_PLUGINS_TO_UPDATE="PLACEHOLDER"

export YOUR_JENKINS_URL="PLACEHOLDER"

export PATH_TO_JENKINS_UPDATE_CENTER="PLACEHOLDER"

export PATH_TO_JENKINS_PLUGINS="PLACEHOLDER"
```


### Check the version of Jenkins running.

```shell
${JENKINS_HOME}/jenkins.sh version
```

### List all installed plugins along with their versions.

```shell
${JENKINS_HOME}/jenkins.sh list-plugins
```

### Check if any plugins have updates available.

```shell
${JENKINS_HOME}/jenkins.sh list-plugins | grep -v ')$' | awk '{ print $1 }' | xargs ${JENKINS_HOME}/jenkins.sh install-plugin
```

### Verify the status of updated plugins.

```shell
${JENKINS_HOME}/jenkins.sh list-plugins | grep -v ')$'
```

### Restart Jenkins for changes to take effect.

```shell
${JENKINS_HOME}/jenkins.sh restart
```

### The system administrator may have overlooked plugin update notifications and failed to update them in a timely manner.

```shell


#!/bin/bash



# Set the path to the Jenkins plugins directory

PLUGINS_DIR=${PATH_TO_JENKINS_PLUGINS}



# Get a list of all installed plugins

INSTALLED_PLUGINS=$(ls $PLUGINS_DIR)



# Set the path to the Jenkins update center

UPDATE_CENTER=${PATH_TO_JENKINS_UPDATE_CENTER}



# Get a list of all available plugin updates from the update center

AVAILABLE_UPDATES=$(curl $UPDATE_CENTER/update-center.json | grep -o '\"name\": \"[^\"]*\"' | awk -F ':' '{print $2}' | sed 's/\"//g')



# Check if any installed plugins have available updates

for plugin in $INSTALLED_PLUGINS; do

  if [[ $AVAILABLE_UPDATES =~ $plugin ]]; then

    echo "Plugin '$plugin' has an available update."

  fi

done


```


### During the maintenance window, update the plugins by either manually downloading them from the Jenkins update center or by using a plugin manager tool like Jenkins CLI or Jenkins Configuration as Code.

```shell


#!/bin/bash



# Define variables

JENKINS_URL="${YOUR_JENKINS_URL}"

JENKINS_USERNAME="${YOUR_JENKINS_USERNAME}"

JENKINS_PASSWORD="${YOUR_JENKINS_PASSWORD}"

PLUGINS="${LIST_OF_PLUGINS_TO_UPDATE}"



# Download Jenkins CLI

wget "${JENKINS_URL}/jnlpJars/jenkins-cli.jar"



# Install plugins using Jenkins CLI

java -jar jenkins-cli.jar -s "${JENKINS_URL}" -auth "${JENKINS_USERNAME}:${JENKINS_PASSWORD}" install-plugin ${PLUGINS}



# Restart Jenkins to apply the changes

java -jar jenkins-cli.jar -s "${JENKINS_URL}" -auth "${JENKINS_USERNAME}:${JENKINS_PASSWORD}" restart


```


Jenkins Outdated Plugins Incident

Overview

Parameters

Debug

Check the version of Jenkins running.

List all installed plugins along with their versions.

Check if any plugins have updates available.

Verify the status of updated plugins.

Restart Jenkins for changes to take effect.

The system administrator may have overlooked plugin update notifications and failed to update them in a timely manner.

Repair

During the maintenance window, update the plugins by either manually downloading them from the Jenkins update center or by using a plugin manager tool like Jenkins CLI or Jenkins Configuration as Code.

Learn more

Related Runbooks

Tomcat Server Crash

Tomcat SSL Handshake Failure Incident

Tomcat JVM OutOfMemory Incident

Spark executor failure during job execution.

Support