Fix for Jenkins slowness when Running in cloud

Users deploying Jenkins on cloud instances, including AWS EC2 under the free tier, often encounter sluggish UI loading times post-instance restarts due to dynamic IP address assignment. This article explores the root cause of the issue and offers solutions applicable to cloud deployments beyond AWS.

Description: Users deploying Jenkins on cloud instances often encounter sluggish UI loading times post-instance restarts due to dynamic IP address assignment. This article explores the root cause of the issue and offers solutions applicable to cloud deployments.

Root Cause Analysis:

The primary reason for sluggish Jenkins UI loading across cloud instances, particularly in environments without Elastic IP usage, lies in the dynamic allocation of IP addresses. With each instance restart, cloud platforms allocate new IP addresses. Consequently, Jenkins attempts to utilize outdated IP addresses, resulting in significant delays in UI responsiveness.

Solution Options:

Option 1: Manual Configuration via Command Line

Step 1: Access the Cloud Instance

Utilize Git bash or an SSH tool to log in to the Jenkins cloud instance.

Step 2: Navigate to Jenkins Installation Directory

Execute the following command to navigate to the Jenkins installation directory:

cd /var/lib/jenkins/

Step 3: Modify Configuration File

Edit the "jenkins.model.JenkinsLocationConfiguration.xml" file using a text editor (e.g., Nano):

sudo nano jenkins.model.JenkinsLocationConfiguration.xml

Option 2: Using Jenkins UI

Step 1: Navigate to Manage Jenkins

Go to "Manage Jenkins" in the Jenkins UI.

Step 2: Access System Configuration

Navigate to "Configure System" under "Manage Jenkins."

Step 3: Change Public URL

Locate the "Jenkins URL" field and update it with the current Jenkins URL.

Step 4: Apply Changes

Click on "Apply" and then "Save" to apply the changes.