# Jenkins version Upgrade in RHEL 8.5 **URL:** \ **Category:** Using Jenkins\ **Created:** [September 28, 2024, 3:41am UTC](https://community.jenkins.io/t/jenkins-version-upgrade-in-rhel-8-5/20303 "2024-09-28T03:41:59Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [September 28, 2024, 11:16am UTC](https://community.jenkins.io/t/jenkins-version-upgrade-in-rhel-8-5/20303/2 "2024-09-28T11:16:41Z")
> [@Spandana](#): > > I want to upgrade Jenkins version from 2.319.1 to latest LTS version > > - Do I need to follow any levels to reach final version or directly can we shift from current version to latest version? You’re making a good choice to upgrade. There are multiple critical security vulnerabilities in your current Jenkins version. You should also upgrade your operating system, since Red Hat Enterprise Linux 8.10 is the currently released version of Red Hat Enterprise Linux 8. That’s a very large change in Jenkins versions. The Jenkins project recommends that users upgrade LTS versions every month. You’ve not upgraded in 32 months. You should plan to spend time evaluating and testing the upgrade in a copy of your environment before you attempt it on the production installation. You’re paying 32 months of upgrade debt. Here are some of the answers that have been previously given. Refer to them for more details > [@Best Jenkins Upgrade Path](https://community.jenkins.io/t/best-jenkins-upgrade-path/6266/2): > > Depends greatly on your definition of best. Most reliable: Upgrade all the plugins you can Upgrade to next jenkins stable release follow [Jenkins LTS Upgrade Guide](https://www.jenkins.io/doc/upgrade-guide/) Upgrade all plugins you can Repeat until you are at the most recent version Easiest Shortest: YOLO Make a backup of your config. Install latest into a new directory/server/etc Copy jobs from old one Startup jenkins Install all the plugins you used to have. There’s no quick and easy and reliable way to upgrade 251-\>387 which is … > [@Recommended Upgrade Path Jenkins -?](https://community.jenkins.io/t/recommended-upgrade-path-jenkins/8847/4): > > That is a very large increment of Jenkins versions, spanning multiple significant changes in the Jenkins project. Information about those significant changes are in the [LTS changelog](https://www.jenkins.io/changelog-stable/) and in the [upgrade guides](https://www.jenkins.io/doc/upgrade-guide/). Read the changelog and the upgrade guide very carefully. Your organization has chosen to not upgrade Jenkins for 3 years. That has created some “upgrade debt” that you’ll now need to repay. @mwp565733 shared experience with that type of upgrade in a blog post. It is worthwhile readi… The [Jenkins LTS upgrade guides](https://www.jenkins.io/doc/upgrade-guide/) describe the changes from your current version to the most recent Jenkins LTS. Read the upgrade guides to identify areas that may be important to your installation. Some of the key changes between those two versions include: - Uses Java 17 or Java 21 instead of Java 8 - Fixes for critical security vulnerabilities - Includes multiple user interface improvements - Removes multiple outdated components The [Jenkins LTS changelog](https://www.jenkins.io/changelog-stable/) describes the details of each of the releases between your current release and the most recent release. Read the changelogs for each of the intervening releases and identify areas that may be important to your organization. @mwp565733 shared an upgrade experience in a Jenkins blog post. Read the blog post: > **[Back of the Napkin Guide to Updating Jenkins, for the uninitiated](https://www.jenkins.io/blog/2023/10/31/marc-s-napkin-upgrade-guide/)** > > Jenkins – an open source automation server which enables developers around the world to reliably build, test, and deploy their software > [@Spandana](#): > > - Do we need to upgrade plugins as well after the Jenkins version upgrade or what steps should be followed for plugins? Yes, you’ll need to install the most recent version of the plugins you currently have installed. This is also a time to remove deprecated plugins and to remove plugins with known security vulnerabilities. The Jenkins plugins site now includes a plugin health score for each plugin. This is a good time to evaluate if there are plugins that should be removed because they are not being maintained or because they are no longer being used. > [@Spandana](#): > > - Please provide the steps to follow for Jenkins version upgrade as this is using by multiple product team, we want to make sure to follow best practices If multiple product teams are using the system, then I assume they care very much that the upgrade runs smoothly with very little downtime. If so, then follow the recommendations in the mentioned posts by creating a backup of the current installation and performing the upgrade on that backup. Confirm the upgrade works on the backup in all the cases that are important to your organization. --- _[View the full topic](https://community.jenkins.io/t/jenkins-version-upgrade-in-rhel-8-5/20303)._