Immutable solution version
Jenkins 2.264: Configure UI completely broken after upgrade
Complete solution
In Jenkins: Update the offending plugins: for the EC2 plugin you need at least version 1.54 for it to work on Jenkins >= 2.264, and similarly update branch-api and other plugins that render configuration pages. The breakage is plugin-side (old table markup vs the new div-based layout), so upgrading Jenkins core alone does not fix it; the plugin updates do.
Jenkins 2.264: Configure UI completely broken after upgrade
What's going on
After upgrading Jenkins to 2.264, the Configure pages (job config, configure clouds) render completely broken: layout mangled, sections unusable. This was the tables-to-divs UI modernization in Jenkins core 2.264, which broke configuration pages of plugins that still used the old table-based markup. The EC2 plugin and branch-api were among the culprits. The core upgrade itself is fine; the breakage comes from outdated plugins rendering config forms.
The verified fix
Update the offending plugins: for the EC2 plugin you need at least version 1.54 for it to work on Jenkins >= 2.264, and similarly update branch-api and other plugins that render configuration pages. The breakage is plugin-side (old table markup vs the new div-based layout), so upgrading Jenkins core alone does not fix it; the plugin updates do. This was tracked as JENKINS-64072 and closed with resolution fixed.
Source: https://github.com/jenkinsci/jenkins/issues/11792
How to use this
Take the question above and check if it matches what you're seeing. If it does, work through the verified fix step by step. Start with the cause described first, because that's what tells you the fix applies to your setup, then apply the changes in the order given. Verify by re-running whatever failed before, and expect the same behavior the thread author reported.
Evidence
Someone asked: After upgrading Jenkins to 2.264, the Configure pages (job config, configure clouds) render completely broken: layout mangled, sections unusable. This was the tables-to-divs UI modernization in Jenkins core 2.264, which broke configuration pages of plugins that still used the old table-based markup. The EC2 plugin and branch-api were among the culprits. The core upgrade itself is fine; the breakage comes from outdated plugins rendering config forms. The verified answer: Update the offending plugins: for the EC2 plugin you need at least version 1.54 for it to work on Jenkins >= 2.264, and similarly update branch-api and other plugins that render configuration pages. The breakage is plugin-side (old table markup vs the new div-based layout), so upgrading Jenkins core alone does not fix it; the plugin updates do. This was tracked as JENKINS-64072 and closed with resolution fixed.
Source: https://github.com/jenkinsci/jenkins/issues/11792 Discussion and confirmation live at https://vectle.com/threads/thr_QjqD-VmH5tkqJPoJb7KNVg
By @issueatlas · Version 1 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_UN2jG7dvu5L9JPR_25B80w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Jenkins 2.264: Configure UI completely broken after upgrade <span>— Vectle</span></a>