# Upgrade from 2.452.3 to 2.516.2 failed

**URL:** <https://community.jenkins.io/t/upgrade-from-2-452-3-to-2-516-2-failed/35545>\
**Category:** Using Jenkins\
**Tags:** question\
**Created:** [September 4, 2025, 1:05pm UTC](https://community.jenkins.io/t/upgrade-from-2-452-3-to-2-516-2-failed/35545 "2025-09-04T13:05:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jumpingkangaroo](https://avatars.discourse-cdn.com/v4/letter/j/7ba0ec/32.png) [@jumpingkangaroo](https://community.jenkins.io/u/jumpingkangaroo)\
**Post date:** [September 4, 2025, 1:05pm UTC](https://community.jenkins.io/t/upgrade-from-2-452-3-to-2-516-2-failed/35545/1 "2025-09-04T13:05:07Z")

</div>

Jenkins setup:

Current version: 2.452.3 running on Ubuntu 22.04

Hi,

I’m trying to upgrade our Jenkins server from 2.452.3 to the latest 2.516.2. I ran the upgrade via apt update but after rebooting I am getting a lot of plugin errors which i believe is stopping Jenkins form starting.

SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin GitHub plugin v1.39.0 (github)

SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin GitHub Branch Source Plugin v1789.v5b\_0c0cea\_18c3 (github-branch-source)

SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: GitHub Groovy Libraries v61.v629f2cc41d83 (pipeline-github-lib)

etc

I didn’t update the plugin’s before upgrading. Is this something I should have done first?

Any help getting this up and running will be most appreciated.

Thanks

James

---

<div class="post-metadata">

**Author:** ![mawinter69](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/mawinter69/32/1625_2.png) [@mawinter69](https://community.jenkins.io/u/mawinter69)\
**Post date:** [September 4, 2025, 3:31pm UTC](https://community.jenkins.io/t/upgrade-from-2-452-3-to-2-516-2-failed/35545/2 "2025-09-04T15:31:57Z")

</div>

Yes you most likely have many plugins that need to be updated. Potentially it is only a few plugins that make problems so you need to identify them. In the logs look for the first plugin that fails to load and check whey it is not loading, probably it requires another plugin in a newer version. So update that plugin. But that approach might take several rounds until Jenkins comes up so you can then use the UI to update all remaining plugins.

What might be easier is to use the [GitHub - jenkinsci/plugin-installation-manager-tool: Plugin Manager CLI tool for Jenkins](https://github.com/jenkinsci/plugin-installation-manager-tool) . For this you need to create a list of all your plugins, then call the tool and it will download all plugins.

---

<div class="post-metadata">

**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 4, 2025, 3:42pm UTC](https://community.jenkins.io/t/upgrade-from-2-452-3-to-2-516-2-failed/35545/3 "2025-09-04T15:42:41Z")

</div>

The steps for an upgrade are usually:

1. Read the [upgrade guide](https://www.jenkins.io/doc/upgrade-guide/) for your version and any intervening versions. Optionally, watch the [“What’s New in Jenkins LTS”](https://www.youtube.com/playlist?list=PLvBBnHmZuNQJeznYL2F-MpZYBUeLIXYEe) videos
2. Update plugins to most recent releases supported on that version of Jenkins
3. Update Jenkins to most recent release
4. Update plugins to most recent releases

Upgrade guides for your specific versions will describe major changes that happened between those releases, including

- Several important security fixes
- Spring Security 6 upgrade
- Java 17 required as minimum Java version
- YahooUI JavaScript library removed
- Navigation and header redesign

There is also a blog post that outlines the upgrade process

> **[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

---

<div class="post-metadata">

**Author:** ![jumpingkangaroo](https://avatars.discourse-cdn.com/v4/letter/j/7ba0ec/32.png) [@jumpingkangaroo](https://community.jenkins.io/u/jumpingkangaroo)\
**Post date:** [September 4, 2025, 3:46pm UTC](https://community.jenkins.io/t/upgrade-from-2-452-3-to-2-516-2-failed/35545/4 "2025-09-04T15:46:09Z")

</div>

Thanks for the reply. I had a feeling it may be an update failing to start but i was on limited time so had to rollback.  
I`m creating a clone to work out what was failing. Can plugins be updated via the terminal?

---

<div class="post-metadata">

**Author:** ![mawinter69](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/mawinter69/32/1625_2.png) [@mawinter69](https://community.jenkins.io/u/mawinter69)\
**Post date:** [September 4, 2025, 5:45pm UTC](https://community.jenkins.io/t/upgrade-from-2-452-3-to-2-516-2-failed/35545/5 "2025-09-04T17:45:56Z")

</div>

yes with the plugin manager tool you download the plugins from command line. Either directly into the plugins directory of your instance or you download them in a separate folder and copy them afterwards.
