# Help upgrading a long neglected Jenkins install

**URL:** <https://community.jenkins.io/t/help-upgrading-a-long-neglected-jenkins-install/10996>\
**Category:** Using Jenkins\
**Created:** [November 28, 2023, 1:32pm UTC](https://community.jenkins.io/t/help-upgrading-a-long-neglected-jenkins-install/10996 "2023-11-28T13:32:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![zeunasc](https://avatars.discourse-cdn.com/v4/letter/z/898d66/32.png) [@zeunasc](https://community.jenkins.io/u/zeunasc)\
**Post date:** [November 28, 2023, 1:32pm UTC](https://community.jenkins.io/t/help-upgrading-a-long-neglected-jenkins-install/10996/1 "2023-11-28T13:32:21Z")

</div>

Today I inherited the Jenkins server that our Legacy team uses to maintain older version of our applications. It hasn’t been updated in years, and I’m asked to get it upgraded so that it stops getting dinged on our vulnerability scans. I’ve tried using this video: [https://www.youtube.com/watch?v=fEO7dOxHvgU&t=144s](https://www.youtube.com/watch?v=fEO7dOxHvgU&t=144s) but my Support Core plugin won’t work, it says that it’s built for Jenkins 2.361.4 or newer and won’t run. I’ve also read through a few posts on this forum, but they seem heavy on broad concepts, light on actual help. Can someone point me in the right direction?

Thanks in advance,  
Tim

Jenkins setup:

## Jenkins: 2.347 OS: Windows Server 2016 - 10.0 Java: 1.8.0\_144 - Oracle Corporation (Java HotSpot™ Client VM)

ace-editor:1.1  
antisamy-markup-formatter:1.5  
apache-httpcomponents-client-4-api:4.5.13-1.0  
bootstrap4-api:4.6.0-4  
bootstrap5-api:5.1.3-6  
bouncycastle-api:2.26  
build-timeout:1.20  
caffeine-api:2.9.3-65.v6a\_47d0f4d1fe  
checks-api:1.7.3  
cloudbees-folder:6.714.v79e858ef76a\_2  
command-launcher:81.v9c2cb\_cb\_db\_392  
config-file-provider:3.9.0  
credentials:1087.1089.v2f1b\_9a\_b\_040e4  
credentials-binding:523.vd859a\_4b\_122e6  
display-url-api:2.3.6  
durable-task:496.va67c6f9eefa7  
echarts-api:5.3.2-1  
email-ext:2.88  
envinject:2.854.vfa\_1657078c97  
envinject-api:1.199.v3ce31253ed13  
font-awesome-api:6.0.0-1  
git:4.11.1  
git-client:3.11.0  
git-parameter:0.9.16  
git-server:1.10  
htmlpublisher:1.30  
jackson2-api:2.13.2.20220328-273.v11d70a\_b\_a\_1a\_52  
javax-activation-api:1.2.0-3  
javax-mail-api:1.6.2-6  
jdk-tool:1.5  
jquery:1.12.4-1  
jquery3-api:3.6.0-3  
jsch:0.1.55.2  
junit:1.63  
mailer:414.vcc4c33714601  
matrix-auth:2.6.6  
matrix-project:771.v574584b\_39e60  
msbuild:1.30  
okhttp-api:4.9.3-105.vb96869f8ac3a  
pam-auth:1.8  
plain-credentials:1.8  
plugin-util-api:2.16.0  
popper-api:1.16.1-3  
popper2-api:2.11.5-1  
resource-disposer:0.19  
ruby-runtime:0.12  
scm-api:608.vfa\_f971c5a\_a\_e9  
script-security:1158.v7c1b\_73a\_69a\_08  
simple-theme-plugin:103.va\_161d09c38c7  
snakeyaml-api:1.30.1  
ssh-agent:1.24.1  
ssh-credentials:277.v95c2fec1c047  
ssh-slaves:1.29.4  
sshd:3.228.v4c9f9e652c86  
structs:318.va\_f3ccb\_729b\_71  
timestamper:1.13  
token-macro:293.v283932a\_0a\_b\_49  
trilead-api:1.57.v6e90e07157e1  
variant:1.4  
windows-slaves:1.8  
workflow-api:1144.v61c3180fa\_03f  
workflow-cps:2689.v434009a\_31b\_f1  
workflow-cps-global-lib:570.v21311f4951f8  
workflow-durable-task-step:2.38  
workflow-job:1180.v04c4e75dce43  
workflow-scm-step:399.v9b\_8f4da\_65061  
workflow-step-api:625.vd896b\_f445a\_f8  
workflow-support:819.v37d707a\_71d9b\_  
ws-cleanup:0.42

---

<div class="post-metadata">

**Author:** ![zeunasc](https://avatars.discourse-cdn.com/v4/letter/z/898d66/32.png) [@zeunasc](https://community.jenkins.io/u/zeunasc)\
**Post date:** [November 28, 2023, 1:55pm UTC](https://community.jenkins.io/t/help-upgrading-a-long-neglected-jenkins-install/10996/2 "2023-11-28T13:55:13Z")

</div>

As a follow-up, would it be better/advisable to stand up a fresh Jenkins install and migrate the data to it? Is that even possible?

---

<div class="post-metadata">

**Author:** ![john\_l](https://avatars.discourse-cdn.com/v4/letter/j/c2a13f/32.png) [@john\_l](https://community.jenkins.io/u/john_l)\
**Post date:** [November 29, 2023, 7:46am UTC](https://community.jenkins.io/t/help-upgrading-a-long-neglected-jenkins-install/10996/3 "2023-11-29T07:46:35Z")

</div>

I have done this, but it was on Linux.  
It was awhile ago so I can’t remember the version details, but what I basically did due to no upgrade path, was a fresh install, backup /var/lib/jenkins (jenkins\_home) on the old server, then moved that to the new server and restarted Jenkins. There were some other fiddly steps, but that more to do with our air-gapped network. Plugins were more of an issue, due to dealing with deprecated versions and dependancy hell lol  
I have never done it on windows, so that may have it’s own issues…?  
Good luck with it

---

<div class="post-metadata">

**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\
**Post date:** [November 29, 2023, 9:13am UTC](https://community.jenkins.io/t/help-upgrading-a-long-neglected-jenkins-install/10996/4 "2023-11-29T09:13:18Z")

</div>

Hello @zeunasc and welcome to this community. 👋

Please give a look at: [Back of the Napkin Guide to Updating Jenkins, for the uninitiated](https://www.jenkins.io/blog/2023/10/31/marc-s-napkin-upgrade-guide/) .  
You may find it useful.

---

<div class="post-metadata">

**Author:** ![zeunasc](https://avatars.discourse-cdn.com/v4/letter/z/898d66/32.png) [@zeunasc](https://community.jenkins.io/u/zeunasc)\
**Post date:** [November 29, 2023, 1:03pm UTC](https://community.jenkins.io/t/help-upgrading-a-long-neglected-jenkins-install/10996/5 "2023-11-29T13:03:31Z")

</div>

Thank you both. I was thinking that a fresh install would be the easiest path.