This plugin needs to be updated for the Table to div layout migration. Until a PR to adapt this plugin is proposed, merged, and released, this plugin will remain incompatible with Jenkins 2.264 or later, including Jenkins 2.277.1 LTS and later LTS releases. The only short-term option would be to uninstall the plugin or revert back to a previous Jenkins core release without the tables to divs change.

CC dconneely

Basil just beat me to it. With Jenkins versions 2.263 and 2.262 and earlier, everything is fine. With Jenkins versions 2.264 and 2.265 and later, the UI is broken.  https://issues.jenkins.io/browse/JENKINS-56109 is the change that caused it, and https://issues.jenkins.io/browse/JENKINS-64184 is a reported issue that duplicates this.

Unfortunately I don't know the exact ins-and-outs of the tables-to-divs UI changes that the Jenkins core team have made.

If it helps anyone who knows more than me: change the `<scope>` of the com.serena.dimensions:dmclient dependency to `compile` in pom.xml to be able to see the configuration forms work correctly with `mvn clean hpi:run -Djenkins.version=2.263` and incorrectly with `mvn clean hpi:run -Djenkins.version=2.264`.

I'll also do some research into what element in the Jelly causes the form corruption.

One workaround in the meantime is to downgrade to Jenkins version 2.263 or earlier.

dconneely First of all, great to see that this plugin has an active maintainer! I'm not a member of the Jenkins core team but I can refer you to the instructions in this table-to-div migration documentation for updating your plugin for tables-to-divs. There are also many PRs from plugin conversions that have already been done which can be used as an example; those are linked on the same page. I have not been following this migration too closely; if you have any further questions on the ins-and-outs maybe timja or others from the UX sig on Gitter can help.

Some links found after quick research this morning - probably for my own use, but recording them here in case useful to anyone else:

• https://www.jenkins.io/doc/developer/views/table-to-div-migration/ - page about migration to div-based config form layout. From this and examination of the dimensiosnsscm-plugin Jelly files looks like table elements are the issue.
• https://github.com/jfrog/jenkins-artifactory-plugin/pull/266/files - how a similar issue was solved in the Jenkins Artifactory plugin (uses Jelly XML, so more similar).
• https://github.com/jenkinsci/matrix-auth-plugin/pull/83/files - how the same issue was solved in matrix-auth-plugin (uses Jelly Groovy, so not going to be hugely helpful - although it's clear the fix is the same - use a div instead of a table if a certain variable's set)
• https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=20741 - Dashboard for table-to-divs issues, but page often shows no content except for title and footer for me. After several retries, it currently is showing about 30 other defects (in multiple plugins) which have been assigned the tables-to-divs-regression label.

Thank you both for the help. I was worried because I forgot to add I did copy over all the jar files that I may have only gotten responses back on that. Good to know this is a known issue and it wasn't something I did wrong (other than I shouldn't have upgraded yet). I'll go ahead and try the workaround and downgrade and hope to get this back up and running in the meantime, this is our production environment and I need this fixed ASAP. Is it worth trying to do the table-to-divs migration or should I just wait until the plugin is updated and compatible with the newer versions of Jenkins? After I get my production Jenkins back working, I'll go back to DEV and can mess around with this if you think its worth the time? Thanks again!