jonl_percsol do you have the http_request plugin installed?  https://issues.jenkins-ci.org/browse/JENKINS-64054

If not can you provide a full list of plugins and their versions please:

(source of script https://github.com/jenkinsci/docker#plugin-installation-manager-cli-preview-2)

JENKINS_HOST=username:password@myhost.com:port
curl -sSL "http://$JENKINS_HOST/pluginManager/api/xml?depth=1&xpath=/*/*/shortName|/*/*/version&wrapper=plugins" | perl -pe 's/.*?<shortName>([\w-]+).*?<version>([^<]+)()(<\/\w+>)+/\1 \2\n/g'|sed 's/ /:/'
 

plugin xml attached list attatched.  http_request not directly installed.

I'm experiencing the same issue, can't edit any jobs due to the messed up formatting, save button doesn't work.

I do have the http_request plugin installed. I installed the pre-release plugin version 1.8.27 from the linked issue above, but it didn't seem to have any effect on the formatting.

Yes i am experiencing the same issue 

Jenkins version: 2.264
Java Runtime : Open Jdk 1.8.0_272 from https://adoptopenjdk.net/

Configuration screen is broken and Save and Apply button are not visible

In chrome, dev tools -> console -> I see lot of these errors.

> hudson-behavior.js:49 TypeError: e.getAttribute is not a function
> at findFormParent (hudson-behavior.js:2589)
> at findNearBy (hudson-behavior.js:275)
> at Object.nearBy (hudson-behavior.js:327)
> at hudson-behavior.js:526
> at hudson-behavior.js:47
> at prototype.js:853
> at Array.forEach (<anonymous>)
> at Array.each (prototype.js:852)
> at HTMLInputElement.e.targetUrl (hudson-behavior.js:525)
> at registerValidator (hudson-behavior.js:533)

 I do not have http-request plugin installed.

See attached plugin-list laksh - jenkins plugins.txt

aptalca that will mean you have another plugin installed causing issues, can you provide a full list please

laksh I've reviewed the list and haven't seen any with known issues, I'll find which one is causing it later on

jonl_percsol can you try disabling the artifactory plugin? ref https://github.com/jfrog/jenkins-artifactory-plugin/issues/350  , I've tried with your plugins and more needs disabling, I'll get back to you

laksh is that the full list of plugins? I installed all the plugins on there with their latest versions and I was unable to reproduce.

laksh did you mean job configuration or system configuration?

cat /tmp/plugins.txt | cut -d ' ' -f 1 > /tmp/plugins2.txt
rm -rf ~/.jenkins-tables
export JENKINS_HOME=~/.jenkins-tables
java -jar ~/Downloads/jenkins.war
java -jar ~/Downloads/jenkins-plugin-manager-2.1.0.jar -d ~/.jenkins-tables/plugins/ --war ~/Downloads/jenkins.war -f /tmp/plugins2.txt

I am having the same issue. I've attached a plugins list plugins.txt

We did have http_request which was breaking "Configure System" too but I uninstalled that (along with a lot of other stuff we aren't using). Configure system now works.

I am getting very similar errors from behaviour.js and nothing relavent looking server side. The issue seemed to be triggered on html tags related to bitbucketscm. I am currently running 2.9.2 of Bitbucket Branch Source but 2.9.4 had the same issues and their tracker doesn't have anything yet.

Ideally if the gui gets this broken it should fail to save, we had a situation where all our project behaviours for the master Bitbucket project were lost (so no builds for anyone). Downgrading to 2.263 has resolved this for now.

timja here's a list of all plugins: 

https://pastebin.com/sfPzxBK7

timja on both System Configuration and Job Configuration layout is broken. On job configuration Save & Apply are visible but does not do anything when clicked. And on System configuration these two buttons are not visible.

laksh can you make sure you update all your plugins please? when I installed your plugins system config was fine, (at least without configuring anything)

laksh, jonl_percsol and aptalca

publish over SSH plugin is causing this, which you all have installed, I created https://issues.jenkins-ci.org/browse/JENKINS-64078

jonl_percsol you also have artifactory installed which is https://github.com/jfrog/jenkins-artifactory-plugin/issues/350 

timja,

Thanks for the investigation.  Unfortunately, those two plugins are used by multiple projects and not an easy removal on our end, especially the artifactory one.  I will watch those bugs for updates.

timja I uninstalled publish over ssh, restarted, but still the same issue with the messed up formatting on /configure

Anyone using publish over SSH please update to latest, https://issues.jenkins-ci.org/browse/JENKINS-64078 is fixed and released

lingwocj I wasn't able to reproduce your issue, would you be able to create a new issue and tag me in.

I need screenshots and your existing config (along with the plugin list copied there)

timja

I tried uninstalling the publish over ssh plugin, didn't have any effect.

Then I installed the new patched version, again, no effect.

Here's a new plugin list: https://pastebin.com/FPJQFWHc

Attached are a couple of pics showing the incorrect formatting on a new freestyle project configure page

aptalca yes I know, looking at your plugins currently

aptalca your issue is https://plugins.jenkins.io/urltrigger/  https://issues.jenkins-ci.org/browse/JENKINS-64081

I've re-tested after enabling everything again,

disabling http_request and urltrigger fixes the issue for me using your plugins

I think I've triaged all issues, except for Chris's issue which I can't reproduce.

Please let me know if this isn't the case.

timja thanks so much for identifying and confirming. Unfortunately we have a lot of jobs that rely on the urltrigger plugin so we'll have to wait until it's fixed.

I should have a fix for urltrigger tomorrow morning UTC time, it looks straightforward. 

timja It is slightly different perhaps to these other issues, I'd probably have reported it to Bitbucket Branch Source Plugin if I'd not found this. The problem exists in their latest version and the previous, but only in Jenkins 2.264. Everything works fine in 2.263.

If I create a new Bitbucket Team/Project it wont save the "Repository Source" and it comes up blank on editing. If I then create the source again and add a behaviour, the source isn't there after a save. If I don't add the behaviour then the source will save despite the js error.

This js error appears after creating the new repository source during an edit. I saw no js errors when creating a new project.

I can report this in their git repo if you would prefer.

There’s a separate branch api ticket which is likely the cause of that one

We are having this issue on the configure Project page, similar to the images aptalca posted above.
List of plugins here Plugins.txt

 Browser console presents several of these JS errors related to several different properties

behavior.js:119 TypeError: Cannot read property 'hasClassName' of undefined
    at repeatable.js:159
    at Array.forEach (<anonymous>)
    at behavior.js:116
    at Array.forEach (<anonymous>)
    at behavior.js:111
    at Array.forEach (<anonymous>)
    at Object.applySubtree (behavior.js:93)
    at Object.apply (behavior.js:76)
    at behavior.js:71
    at window.onload (behavior.js:133)

List of plugins: plugins.txt

Console error when loading pipeline project

behavior.js:119 TypeError: Cannot read property 'hasClassName' of undefined
    at VM3783 repeatable.js:159
    at Array.forEach (<anonymous>)
    at behavior.js:116
    at Array.forEach (<anonymous>)
    at behavior.js:111
    at Array.forEach (<anonymous>)
    at Object.applySubtree (behavior.js:93)
    at Object.apply (behavior.js:76)
    at behavior.js:71
    at window.onload (behavior.js:133)
behavior.js:119 TypeError: Cannot read property 'next' of undefined
    at findEnd (hudson-behavior.js:808)
    at hudson-behavior.js:1109
    at Array.forEach (<anonymous>)
    at behavior.js:116
    at Array.forEach (<anonymous>)
    at behavior.js:111
    at Array.forEach (<anonymous>)
    at Object.applySubtree (behavior.js:93)
    at Object.apply (behavior.js:76)
    at behavior.js:71
behavior.js:119 TypeError: Cannot read property 'hasClassName' of undefined
    at hudson-behavior.js:1146
    at Array.forEach (<anonymous>)
    at behavior.js:116
    at Array.forEach (<anonymous>)
    at behavior.js:111
    at Array.forEach (<anonymous>)
    at Object.applySubtree (behavior.js:93)
    at Object.apply (behavior.js:76)
    at behavior.js:71
    at window.onload (behavior.js:133)
behavior.js:119 TypeError: Cannot read property 'makeInnerVisible' of undefined
    at updateOptionalBlock (hudson-behavior.js:1528)
    at hudson-behavior.js:1167
    at Array.forEach (<anonymous>)
    at behavior.js:116
    at Array.forEach (<anonymous>)
    at behavior.js:111
    at Array.forEach (<anonymous>)
    at Object.applySubtree (behavior.js:93)
    at Object.apply (behavior.js:76)
    at behavior.js:71
behavior.js:119 TypeError: Cannot read property 'makeInnerVisible' of undefined
    at updateDropDownList (hudson-behavior.js:1236)
    at hudson-behavior.js:1250
    at Array.forEach (<anonymous>)
    at behavior.js:116
    at Array.forEach (<anonymous>)
    at behavior.js:111
    at Array.forEach (<anonymous>)
    at Object.applySubtree (behavior.js:93)
    at Object.apply (behavior.js:76)
    at behavior.js:71

Having the same problem here. I don't have any of the above mentioned plugins. plugin.txt

For us it was the fstrigger plugin which was causing this - removing it resolved the issue.

javadevil Thanks! fstrigger was the issue for me too

seineriver you have the artifactory plugin installed https://github.com/jfrog/jenkins-artifactory-plugin/issues/350

Dik and Chris thanks, I'm looking at that plugin currently, seems it hasn't been touched in a very long time...

I've created JENKINS-64139 for fstrigger, it's got quite a low install base, and it needs some work to be updated for testing it properly.

Let us know on the issue if you need it fixed otherwise I'm going to look at more important plugins first

FYI,

I don't have the fstrigger or artifcatory plugin installed and also have the same issue when upgrading to 2.265

How can you tell which plugin is causing this issue ? Enable/disable them one by one ?

I normally do it in groups of 10 or so but yes disable until you figure it out

I've disabled dozens of plugins and I haven't been able to narrow it down yet.  It doesn't seem obvious what plugins are causing it from the browser console logs, either.  It looks like it's specific to the web UI though, so for now I'm hacking the job XML and reloading from disk as a workaround, which isn't fun, but at least it will keep jobs running for now.

I'll share how I found my problem plugin in case this also helps other narrow it down.

By looking at the config screen and seeing which was the last plugin to be correctly be rendered in the center div (green arrow), red arrow incorrect and where the problems started.
(NB: Reusing someone else screenshot here as I don't have the problem to take my own)
Then I looked at the help of those to see which plugin it was (orange box), checked the github repo and inspected the config.jelly files to see if they used table tags.

vwbusguy

can you post a plugin list please:
https://issues.jenkins-ci.org/browse/JENKINS-64072?focusedCommentId=400146&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-400146

timja I hope you don't mind the ping, but with the two plugins (urltrigger and hhtp request) updated, all of our issues are solved.

I also wanted to thank you for your efforts. Not only you identified all of our issues, but you submitted PRs to some of those plugins to fix the issues upstream. You're the real MVP.

timja  Thanks for all your work getting this straightened out!

I haven't been able to track down the cause for our install.  Here is a list of our enabled plugins at the moment:  https://gist.github.com/LaCuneta/206aa658103a1059f8e91c1bae8d055f

I did a bunch of disabling of plugins we don't use and got some of our basic jobs editable again, but our multi-branch pipeline jobs still error out.  Maybe that plugin itself is affected?

Like Scott Williams I've managed to get around it by hand-editing config files for now.

Here is the error that we see in the web console:

behavior.js:119 TypeError: Cannot read property 'firstElementChild' of undefined
    at findNeighboringDynamicInput (VM103 github-scm-source.js:25)
    at VM103 github-scm-source.js:30
    at Array.forEach (<anonymous>)
    at behavior.js:116
    at Array.forEach (<anonymous>)
    at behavior.js:111
    at Array.forEach (<anonymous>)
    at Object.applySubtree (behavior.js:93)
    at Object.apply (behavior.js:76)
    at behavior.js:71

Editing pipeline jobs is being worked in the branch api ticket. And yeah aware of that issue too

Thanks javadevil for giving those instructions. I've managed to find out the responsible files for UI-issues on my installation:

https://github.com/jenkinsci/artifactory-plugin/blob/artifactory-3.9.0/src/main/resources/org/jfrog/hudson/ArtifactoryRedeployPublisher/config.jelly
https://github.com/jenkinsci/artifactory-plugin/blob/artifactory-3.9.0/src/main/resources/org/jfrog/hudson/generic/ArtifactoryGenericConfigurator/config.jelly
https://github.com/jenkinsci/artifactory-plugin/blob/artifactory-3.9.0/src/main/resources/org/jfrog/hudson/gradle/ArtifactoryGradleConfigurator/config.jelly
https://github.com/jenkinsci/artifactory-plugin/blob/artifactory-3.9.0/src/main/resources/org/jfrog/hudson/ivy/ArtifactoryIvyFreeStyleConfigurator/config.jelly
https://github.com/jenkinsci/artifactory-plugin/blob/artifactory-3.9.0/src/main/resources/org/jfrog/hudson/ivy/ArtifactoryIvyConfigurator/config.jelly
https://github.com/jenkinsci/artifactory-plugin/blob/artifactory-3.9.0/src/main/resources/org/jfrog/hudson/maven3/ArtifactoryMaven3Configurator/config.jelly
https://github.com/jenkinsci/artifactory-plugin/blob/artifactory-3.9.0/src/main/resources/org/jfrog/hudson/maven3/ArtifactoryMaven3Configurator/config.jelly

jbb1 if you build https://github.com/jenkinsci/branch-api-plugin/pull/228 from source I think it should fix your issue. (mvn clean package -P quick-build) (java 8 or 11), result will be in the target directory as a .hpi file.

Worth testing.

CI can't build it to generate an rc build unfortunately because it needs a change in the CI file.

Regarding these vertical dashed lines, why are they there, and can they be removed? Every configuration screen is visually poor now, bad user experience.

Can you create a separate issue for that borisivan include screenshots on where it doesn’t looks good please

All major plugins with issues except the artifactory plugin are now fixed, please upgrade to latest plugins and Jenkins 2.266

timja : Upgraded all plugins & jenkins build to Jenkins 2.266. Still the problem persists. Attached the list of plugins. Could you please let me know if any of the plugin is causing the problem and what we need to do.jenkins-basith-11112020.txt

basith you are using the artifactory plugin, please disable and see if it's still an issue

timja I am still seeing this issue on Jenkins 2.266 with the latest version of all plugins.

Attaching my plugin list: plugins.rossc.txt

Here's a screenshot of how the config page breaks - others mentioned this may be useful:

Can you use the script from the first comment please? I can then create an environment to reproduce it

I had a quick look and can’t see one with a known issue

timja my apologies, I did not see that due to the number of comments, here it is: plugins.rossc-2.txt

Thanks I’ll look tomorrow

Hi timja, I can add additional screenshots, but all the ones here in the comments already illustrate the issue. The presence of the vertical dashed lines to logically group things that are already grouped via indentation is ugly and distracting. Can they be removed, or at least off by default? Maybe if some people need them, they could enable with a non default option in "configure system" or something like that.

Boris that is a very different issue please move the discussion on that to a new one

Hi rossc

Can you please test this pre-release version of postbuild-task:

https://repo.jenkins-ci.org/incrementals/org/jvnet/hudson/plugins/postbuild-task/1.9-rc62.454e8cf3c106/postbuild-task-1.9-rc62.454e8cf3c106.hpi

the issue for that plugin is: JENKINS-64088, there appears to be no maintainer.

I requested commit access in https://groups.google.com/g/jenkinsci-dev/c/08iLU7F8RfQ/m/pqrbtqp2AwAJ
(there's a two week timeout and if no response I'll get it)

In my case it was the old Perforce Plugin (not the P4 one) that broke the job configuration page.

timja this version fixed one of my jobs (incidentally, the one that uses copyartifact), but not most of them unfortunately.. the visual appearance has changed, so I believe this was a fix and there are additional issues elsewhere.  The job configuration page now looks like below - there is no longer the gray box around the configuration items that gets "broken out of" so to speak.  

That looks like the plot plugin there’s a separate issue for that one, I’ll link it to this after I find it

The same issue is on my side, centos, Jenkins v.263->v.264 - cannot save/edit some job configurations, reverted to 263.

brababus please provide a full plugins list

JENKINS_HOST=username:password@myhost.com:port
curl -sSL "http://$JENKINS_HOST/pluginManager/api/xml?depth=1&xpath=/*/*/shortName|/*/*/version&wrapper=plugins" | perl -pe 's/.*?<shortName>([\w-]+).*?<version>([^<]+)()(<\/\w+>)+/\1 \2\n/g'|sed 's/ /:/'

I uninstalled plot for now, and can configure all my jobs again - many thanks for all your hard work on this timja it is very much appreciated!

Postbuild task plugin fixed in https://github.com/jenkinsci/postbuild-task-plugin/releases/tag/postbuild-task-1.9

jenkins-basith-16112020.txt

timja Removed artifactory plugins and issue remains the same, I double checked no plot plugin as well. Could you please check and let me know if there is any other plugin causing the issue.

Similar issue with me. No artifactory or plot plugins. latest branch api and jenkins core. timja any thoughts?

plugins.txt

cryptomatt your plugins list says you're not on the latest branch-api?

Could you please include a screenshot too and say which page it is on

basith you have a lot of plugins :O 323.

You can setup a test environment with:

curl https://issues.jenkins.io/secure/attachment/53350/53350_jenkins-basith-16112020.txt | sort > abdul-bas-plugins.txt
wget https://github.com/jenkinsci/plugin-installation-manager-tool/releases/download/2.1.2/jenkins-plugin-manager-2.1.2.jar
wget https://get.jenkins.io/war/2.266/jenkins.war
export JENKINS_HOME=~/.jenkins-64072
java -jar jenkins-plugin-manager-2.1.2.jar -f abdul-bas-plugins.txt -d ~/.jenkins-64072/plugins --war jenkins.war
java -jar jenkins.war

and then disable plugins till you find the issue

I had to remove warnings, analysis-core and zap-pipeline as they are no longer available

Thanks timja. Issue was with "Environment Dashboard Plugin" Plugin. Managed to uninstall/disable and it worked.

timja here you go.

in the plugin list its shown as Branch API Plugin (branch-api): 2.6.3

Nice Abdul can you create an issue and add the tables-to-docs-regression label please

Matthew can you do a new plugins export as in your one it had an old version and then take a screenshot of where your issue is not the plugin version

timja  here you go. even after selecting pipeline script from SCM for a simple existing pipeline job it doesnt show any SCM attributes to choose from. Jenkins version is 2.266

not sure but i see this error in the build triggers section although i have not chosen anything

JS console errors as reported by others

For a brand new multibranch pipeline job, the screen is messed up with the GIT URL showing but the save button isnt working and similar JS errors as above.

plugins-18-11.txt

I'm facing the same issue since upgrading from version 2.263.
Here is the pastebin link to my full installed plugin > https://pastebin.com/yVtS6Fck
The paste data is delimited by "|", columns are LongName, Shortname,version, active, url
(The xml plugin list and perl command did not work for me, so I used json and jq instead)

Apart from the behavior.js, hudson js and select js errors reported above, these are the stuff i see from dev console.

At the job configuration screen for a new job, the layout are off and buttons are not working.

And I saw there were some alerts on old data format and this is what I see.

Also facing this issue, plugin list found here: https://pastebin.com/X7XmYT8v

Screenshot of JS errors added:

I tried to go through and disable anything mentioned in this thread. 

My specific issues:

When attempting to load the configuration for a build, the layout is screwed up

I do have the Save/Apply buttons, but clicking Save does nothing, and clicking apply does the following:

Nothing is in the box, so I didn't capture the whole thing.

I first noticed this issue on the Global Security page with the Active Directory plugin active. I figured it was just that plugin since the page was fine with it disabled. However, I'm seeing it now on my build configuration pages as well.  These are the javascript errors I see in the console

I've tried it in Edge (chromium) and IE (whatever the last version before edge was) and same behavior.

Here is the list of my plugins:

https://pastebin.com/p8zkew4p

Hi timja is there an update to this issue? Any workaround that I can apply or is everyone rolling back to the last working Jenkins version?

I haven’t had time to look at your one, you can identify which plugin it is by disabling till it works

Hi timja

Jenkins 2.267
All plugins update

Plugin list found here:1.txt

https://gyazo.com/cb0cd5972ebc4a480bd2f5abf5f128e2

My configure pages and save buttons stopped working

hi timja I have disabled all uninstallable plugins and the problem still remains. 

Hi everyone,

Just to let you know I'm prioritising issues now where people have managed to identify themselves the plugin which is causing the issue.
These show up on the dashboard: https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=20741

Once those are fixed I'll come back here.

Anyone else triaging issues would be much appreciated

The basic flow is:

1. check plugins list against open issues on https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=20741
2. then if no open issue matches:

curl https://issues.jenkins.io/secure/attachment/53350/53350_jenkins-basith-16112020.txt | sort > abdul-bas-plugins.txt
cat abdul-bas-plugins.txt | cut -d ':' -f 1 | sort > plugins.filtered.txt # remove versions as CLI complains when old versions are there
wget https://github.com/jenkinsci/plugin-installation-manager-tool/releases/download/2.1.2/jenkins-plugin-manager-2.1.2.jar
wget https://get.jenkins.io/war/2.266/jenkins.war
export JENKINS_HOME=~/.jenkins-64072
java -jar jenkins-plugin-manager-2.1.2.jar -f abdul-bas-plugins.txt -d ~/.jenkins-64072/plugins --war jenkins.war
java -jar jenkins.war

Normally create a new freestyle job and then reproduce the issue, (requires enough information with steps to reproduce, sometimes it is a different page or requires specific config)
Once reproduced disable plugins in groups of about 10 and record which ones you disabled
Restart Jenkins
If you can still reproduce keep disabling
Once you can't reproduce enable plugins one by one until you find which one it is
Then report an issue with the label 'tables-to-divs-regression'

Artifactory plugin is fixed in the latest release

For those affected by the bitbucket-branch-source-plugin, there's a PR pending release that should fix most issues (https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/399/). This, together with another PR https://github.com/jenkinsci/jenkins/pull/5081 that could be released in Jenkins 2.269 should fix some of these issues.

I managed to find out the "environment-dashboard" plugin is breaking UI in my case
Opened a case and the case can be found here > https://issues.jenkins.io/browse/JENKINS-64336

I'm running on Ubuntu 18.04, seeing this as well.  Several of the already diagnosed plugins are affecting my install.  Disabling them or uninstallng has had no affect.  We're using v2.261, and I've resigned myself to no longer upgrading plugins or version until this is resolved.  I'm not sure why this isn't more a priority, considering that so many plugins have been reported as a possible cause.  Jenkins isn't really useful without it's plugins, and not being to make changes to configurations seems to me to be a bit of an issue.  I also know that I simply don't have time to go through every plugin trying to find the one or two or ten that I need to disable or uninstall so I can upgrade.

Could you provide the list please so it can be fixed?

Apologies, I deleted or uninstalled 4 plugins that were listed in various places and in the several bug tickets associated with this issue.  None of them were plugins I used (they were some of the many that come pre-configured with a default install from way back when, I've never paid attention to them).  I didn't keep track of them because I've never used them.

Hi timja,

following your request from dborin, I've attached here (jenkins plugins in use.txt) the list of plugins installed on our jenkins server. 

We also have the same problem (broken UI, unable to figure which plugin is causing the problem).

Let me know if there is anything else you need to help solve this issue, we are currently using jenkins 2.263.1 in order to work properly.

amidar can you use the script from the top of the issue please? it can be used to build a reproducible environment and it's also a lot easier to read

timja, here is the list after running the script: jenkins plugins in use - correct format.txt

amidar disabling ClearCase Plug-in is enough for free style jobs to work https://issues.jenkins.io/browse/JENKINS-64499

disabling Micro Focus Application Automation Tools is enough for system configuration https://issues.jenkins.io/browse/JENKINS-64500

timja - thanks for the heads up! sadly, those two plugins are still in use (yes, clear case is STILL in use!) in our system.

I noticed recently a member of the praqma team/company who wrote this plugin in the first place sending some update in the developer distribution list, any chance to get their attention on this matter?

I'm certain micro focus will solve this in the next release of their plugin, so i'm not worried about that end.

I’ve tagged the person you mentioned in the other issue

timja, i'm crossing my fingers

amidar have you considered offering to maintain the ClearCase plugin yourself? If you're a ClearCase user, then that likely means you have access to an environment where you could test changes that you make to the ClearCase plugin. Companies that depend on ClearCase are often deeply attached to it because of the large cost to switch to another SCM system. Since your company has already accepted that they won't spend the money to switch to another SCM system, you could ask them instead to fund a person to maintain the Jenkins ClearCase plugin for your use. Your company would benefit from a working ClearCase plugin and the Jenkins community would benefit from your company's work on the plugin.

Unless you have a support contract with Praqma Support, I would not expect them to do any maintenance on the ClearCase plugin. ClearCase is not a heavily used SCM system and it is unlikely that they have access to a ClearCase system any longer.

ruslan_y2020 your issue appears to be the TFS plugin,

that is tracked here: JENKINS-64241

Note the TFS plugin is currently suspended from distribution see INFRA-2751

chasepeeler your issue is the notifications plugin JENKINS-64254, fix is here https://github.com/jenkinsci/notification-plugin/pull/40

and a pre-release version is https://ci.jenkins.io/job/Plugins/job/notification-plugin/job/PR-40/11/artifact/target/notification.hpi

jstr I am unable to reproduce your issue.

Either it has been fixed, I'm missing something, or it's one of the 10 plugins that you have that are either suspended or not distributed from the Jenkins update center.

plugins I couldn't install:

dynamicparameter
encryption-tool-runner
fileoperations-tool-runner
languagerelease-tool-runner
propsfileupdater-tool-runner
setversion-tool-runner
sign-files-plugin
translation-tool-runner
trex-runner
tron-runner

markewaite, regarding your answer on ClearCase - our company moved two years ago to GitLab. since we still have a LOT of legacy, there are still some projects maintained in ClearCase. as much as I would love having the time to maintain the ClearCase plugin, it has no future within our company (and might I add - the entire world).

no sane manager would allocate money/person/time for such a task, I think it would be much easier maintaining a Jenkins server for the legacy projects (on the latest 2.263 LTS line) and another server for everyone else....

sometimes we must admit that backward compatibility breaks - and I have to say I think this time has arrived for us... (unless ewel will prove me wrong, ofcourse...  )

timja Thank you for trying to reproduce the issue.

I checked again today after applying all outstanding updates. I don't see any change. What's still happening, or what the issue may have been reduced to, is a premature bottom end of the list of build steps. The remaining ones are then no longer framed with spacing on the left and right and a grey background. Those build steps that exceed the correctly rendered part of the build step list can then also no longer be dragged and dropped to a different position. Other build steps appear in an entire visual column next to the configure space.

The common denominator between those bugs seems to be the css class "repeated-chunk".

As for the list of plugins you couldn't install, they're all just in-house clones of the Windows Exe Runner plugin, serving as a wrapper/command-line argument sanitizer for smaller tools on the build server. They're not shared publicly since there really isn't any benefit other than parameter-hand-holding. I uploaded one of them to github for the purposes of transparency.

None of them do any more in terms of UI than provide a jelly and a properties file for the installation and the build step each.

jstr can you please upload a full page screenshot or at least a screenshot where the page breaks?

The css class is a symptom of the issue but not really relevant in tracking down where the issue is.

in most cases it's a matter of checking the last plugin before the UI breaks

Hi,
We're having the same issue but in the configureClouds page. other configuration pages seems fine.
I we're using  at least two plugins that are listed here as causing issues (branch-api and env-inject), but since we have production assets relying on this server, I can't currently work on triaging the plugins to figure out which one is causing it or if upgrading the branch-api plugin will fix it.
I need to downgrade the version so we'll be able to work properly. But in case some one can/want to try and pinpoint the issue
Added screenshot configureClouds.png
 
Jenkins version is 2.271. Used plugins: jenkins_plugins.txt

timja Absolutely, they are attached as Project 1 and Project 2, I merely blackened (well, orange'd) some identifying strings

matangoren you need at least version 1.54 of the EC2 plugin for it to work on >=2.264

jstr reproduced, it required adding a build step to the configuration from the Parameterized Trigger plugin, created JENKINS-64502

timja Cheers

davidchin your issue is the environment dashboard plugin, fixed here: https://github.com/jenkinsci/environment-dashboard-plugin/pull/171

The maintainer has been having some issues releasing it, which is tracked here: https://github.com/jenkinsci/environment-dashboard-plugin/issues/173

There's a pre-release version here: https://ci.jenkins.io/job/Plugins/job/environment-dashboard-plugin/job/master/7/artifact/target/environment-dashboard.hpi

cryptomatt I can't reproduce your issue, there's been some branch-api fixes so make sure you're running on the latest version of Jenkins and branch api

I believe all issues on this thread are triaged now,

Please speak up if I missed you.

Could anyone who is waiting for fixes please vote on the issue(s) they are waiting for, https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=20741

I really wish jira server had emoji reactions so you could upvote or downvote this comment if your instance is fixed now

I had the same issue where I couldn't click Save or Apply on any config UI.

Had to remove a couple of old plug-ins to resolve it.

• FindBugs Plug-in
• PMD Plug-in

Had the same issue with the perforce plugin https://plugins.jenkins.io/p4/ possibly because it was used inside the multiple scm plugin https://plugins.jenkins.io/multiple-scms/

Disabling the perforce plugin and keeping multiple scm solved the issue.

thehosh I created JENKINS-64694 to cover that, there's a pull request open to fix it.

I updated to latest 2.277 in our staging environment today and ran all available plugin updates.  

I've tried disabling CVS and Naginator plugins - no success.

plugins.txt

jvanderzouwenTry disabling 10 plugins at a time then restart Jenkins until you've isolated the plugin causing this issue.

jvanderzouwen I believe fstrigger:0.39 will be at least one causing you problems. 

Looks like it is being caused by Active Choices, for me.  If I disable it, the problem goes away.

Actually, it might be Scriptler (which I use within Active Choices) – It seems to be affecting Scriptler's "Edit Script" page also.

crussell52 please create an issue for each of those plugins and add the label 'tables-to-div-regression'

javadevil thanks - I removed and still have the issue.  I'm currently diagnosing to see if I can find the magic combination that lets me update

It ended up being 'locks-and-latches' 0.6.  I've disabled and now the cascading behavior.js issues have subsided.

Has anyone taken a look at the Publish Over FTP Plugin ( https://plugins.jenkins.io/publish-over-ftp/ ) yet?

I have one job for which the UI is still broken, reproduced it by creating a new job and adding build step by build step, saving and re-opening the configure UI after each step.
Once the Publish Over FTP Plugin was added and the page saved, the next time I hit configure, any steps below that build step were broken.

In case you are having trouble replicating this issue, try placing the Publish Over FTP Build Step in a Conditional Build Steps container (i.e., add it as a conditional step) and have some build steps below the nested Publish Over FTP Build Step and/or another build step below the Conditional Build Step container. I hope that description makes sense.

Full Page Screenshot added, with some identifying texts removed:

Of Note: This is not the only problem with the Publish Over FTP Plugin.
Yes, I know this is out-of-scope for this issue, but the question is, should there be a ticket for it? The plugin is up for adoption, so probably no one will look at it.
Anyways, looking at the full page screenshot, the plugin itself is a bit wonky at the moment in its UI. It seems to want to nest Transfer Sets and Target FTP Servers within the build step, but messes up doing either, creating an ambiguous mess of options that can be multiplied.

jstr https://github.com/jenkinsci/publish-over-ftp-plugin/pull/8 and a duplicate PR at https://github.com/jenkinsci/publish-over-ftp-plugin/pull/9

timja Good spot, thanks! The build artifact for it from ci.jenkins.io also looks fine, just manually applied the latest artifact from 25 minutes ago, and it fixes the UI issue.

So now we (well, everyone else) only need to wait for the upload / PR close.

FTR I am releasing a bunch of the plugins as a part of https://groups.google.com/u/1/g/jenkinsci-dev/c/XXztPiLDPmM .

If you see any issues which have not been reported in https://issues.jenkins.io/issues/?jql=labels%20%3D%20tables-to-divs-regression , please submit separate issues

I'm facing the same issue, after dig into job's config xml file and disable some plugin, the source of issue is Android Lint plugin, uninstall it and problem solved.

In update center of my jenkins, Android Lint plugin is deprecated, click learn more, this page (https://issues.jenkins.io/browse/INFRA-2487) show a list of deprecated plugins, such as FindMyBugs/PMD plugin which is mentioned above. 

So when you're facing this issue, please check deprecated plugins in your update center, maybe uninstall those plugins solve this issue.

After an update of Jenkins from 2.263 to 2.291 I faced the issues mentioned here (UI looked strange, changes in job configuration could not be saved).

To get it working again I disabled the following plugins (thanks to Chris Beswick for the instructions how to determine the problem causing plugins fast, see his comment above)

1. Promoted Builds plugin (current version 3.9.1, see also JENKINS-65429)
2. as already mentioned in earlier comments (see above) all deprecated plugins like:
   1. Static analysis suite plugins (Checkstyle, DRY, PMD, Findbugs, Violations)
   2. Multiple SCMs plugin
   3. Locks and latches plugin
   4. Continuous integration game

After some trial and error I found that the rbenv plugin 0.0.17 - jenkins version 2.293
here is how to identify and solve

Open developer tools and inspect the page,
Search for "center" and you will eventually find a plugin or section that modifies the entire page: 
        mine was the div class "optionalBlock-container config_build_environment active"
i tested by changing the align:"center"  to align:"left" 
the name of the block i was in told me which plugin to disable
once i figured out which class was forcing alignment I disabled the plugin of that dependent via manage jenkins plugins
after a reset none of my configure sections auto realigned to the center.

ricfos javadevil toledoe can you please help me with the same. I randomly get DOMException when I save anything on my Jenkins after the upgrade.

Below is the exact error I get. This was when I was trying to configure the Cloud though;

Uncaught DOMException: Blocked a frame with origin "https://domain.com" from accessing a cross-origin frame.
    at HTMLIFrameElement.<anonymous> (https://domain.com/adjuncts/80bde827/lib/form/apply/apply.js:36:66)

Version : Jenkins 2.289.1

We are facing the same issue. However in our case, i cannot see any error message. Neither in the console log of the browser nor in the jenkins log. 

However on the call of the configuration page of a job I can see the following: 

couldn't find the expected parent element (.setting-main) for element

and 

unable to find nearby url

Version: Jenkins 2.289.1

I had already issues in the previous LTS Version so I tried to update the Plugin and also revert the Performance Plugin. 

I am also facing the similar issue. I have upgraded Jenkins from 2.249.2 to 2.289.1 version. Unable to save the global configuration. We are running Jenkins in containerized environment.

I upgraded from 2.249.1 to  2.289.2 (containerized environment) and did not have the save  issue with this list of plugins:

ace-editor:1.1
ansicolor:1.0.0
ant:1.11
antisamy-markup-formatter:2.1
apache-httpcomponents-client-4-api:4.5.13-1.0
authentication-tokens:1.4
badge:1.8
blueocean:1.24.7
blueocean-autofavorite:1.2.4
blueocean-bitbucket-pipeline:1.24.7
blueocean-commons:1.24.7
blueocean-config:1.24.7
blueocean-core-js:1.24.7
blueocean-dashboard:1.24.7
blueocean-display-url:2.4.1
blueocean-events:1.24.7
blueocean-git-pipeline:1.24.7
blueocean-github-pipeline:1.24.7
blueocean-i18n:1.24.7
blueocean-jira:1.24.7
blueocean-jwt:1.24.7
blueocean-personalization:1.24.7
blueocean-pipeline-api-impl:1.24.7
blueocean-pipeline-editor:1.24.7
blueocean-pipeline-scm-api:1.24.7
blueocean-rest:1.24.7
blueocean-rest-impl:1.24.7
blueocean-web:1.24.7
bootstrap4-api:4.6.0-3
bootstrap5-api:5.0.1-2
bouncycastle-api:2.20
branch-api:2.6.4
build-monitor-plugin:1.12+build.201809061734
build-timeout:1.20
caffeine-api:2.9.1-23.v51c4e2c879c8
checks-api:1.7.0
cloudbees-bitbucket-branch-source:2.9.9
cloudbees-folder:6.15
command-launcher:1.6
configuration-as-code:1.51
copyartifact:1.46.1
credentials:2.5
credentials-binding:1.26
cucumber-reports:5.5.0
display-url-api:2.3.5
docker-commons:1.17
docker-workflow:1.26
dtkit-api:3.0.0
durable-task:1.37
echarts-api:5.1.2-2
email-ext:2.83
embeddable-build-status:2.0.3
extended-read-permission:3.2
external-monitor-job:1.7
extra-columns:1.23
favorite:2.3.3
font-awesome-api:5.15.3-3
ghprb:1.42.2
git:4.7.2
git-client:3.7.2
git-server:1.9
github:1.33.1
github-api:1.123
github-branch-source:2.11.1
github-issues:1.2.4
github-pr-coverage-status:2.1.1
github-pullrequest:0.3.0
gitlab-merge-request-jenkins:2.0.0
gitlab-plugin:1.5.20
google-login:1.6
google-oauth-plugin:1.0.6
groovy-postbuild:2.5
handlebars:3.0.8
handy-uri-templates-2-api:2.1.8-1.0
htmlpublisher:1.25
jackson2-api:2.12.3
javadoc:1.6
jdk-tool:1.5
jenkins-design-language:1.24.7
jira:3.5
jjwt-api:0.11.2-9.c8b45b8bb173
jquery:1.12.4-1
jquery-detached:1.2.1
jquery3-api:3.6.0-1
jsch:0.1.55.2
junit:1.51
kerberos-sso:1.7
kubernetes:1.30.0
kubernetes-client-api:5.4.1
kubernetes-credentials:0.9.0
ldap:2.7
lockable-resources:2.11
mailer:1.34
mapdb-api:1.0.9.0
mask-passwords:3.0
matrix-auth:2.6.7
matrix-project:1.19
mercurial:2.12
metrics:4.0.2.8
momentjs:1.1.1
nexus-jenkins-plugin:3.11.20210621-093929.6318134
notification:1.14
oauth-credentials:0.4
oic-auth:1.8
okhttp-api:3.14.9
pam-auth:1.6
pipeline-build-step:2.13
pipeline-github-lib:1.0
pipeline-githubnotify-step:1.0.5
pipeline-graph-analysis:1.11
pipeline-input-step:2.12
pipeline-milestone-step:1.3.2
pipeline-model-api:1.8.5
pipeline-model-definition:1.8.5
pipeline-model-extensions:1.8.5
pipeline-rest-api:2.19
pipeline-stage-step:2.5
pipeline-stage-tags-metadata:1.8.5
pipeline-stage-view:2.19
pipeline-utility-steps:2.8.0
plain-credentials:1.7
plugin-util-api:2.3.0
popper-api:1.16.1-2
popper2-api:2.5.4-2
pubsub-light:1.16
resource-disposer:0.16
robot:3.0.1
role-strategy:3.1.1
ruby-runtime:0.12
scm-api:2.6.4
script-security:1.77
simple-theme-plugin:0.6
snakeyaml-api:1.29.1
sse-gateway:1.24
ssh-agent:1.23
ssh-credentials:1.19
ssh-slaves:1.32.0
ssh-steps:2.0.0
sshd:3.0.3
structs:1.23
subversion:2.14.4
timestamper:1.13
token-macro:2.15
trilead-api:1.0.13
url-auth-sso:1.0
variant:1.4
windows-slaves:1.8
workflow-aggregator:2.6
workflow-api:2.46
workflow-basic-steps:2.23
workflow-cps:2.92
workflow-cps-global-lib:2.21
workflow-durable-task-step:2.39
workflow-job:2.41
workflow-multibranch:2.26
workflow-scm-step:2.13
workflow-step-api:2.23
workflow-support:3.8
ws-cleanup:0.39
xunit:3.0.2
thinBackup

Upgrading to 2.300 version resolved all issues for me

Update to my comment at 2021-05.01 15:05 https://issues.jenkins.io/browse/JENKINS-64072?focusedCommentId=409019&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-409019

With Jenkins 2.293 and promoted builds plugin 3.10 I  can save changes in a job config

I also confirm that getting rid of deprecated plugins helped us (again).

What our Jenkins users/admins actually did:

• they upgraded from Jenkins 2.231 to 2.295 and this issue JENKINS-64072 symptoms started appearing
• warnings about deprecated plugins were ignored for some time
• then we finally sorted out all deprecated plugins - I our current case we uninstalled Findbugs, PMD and Static Analysis Utilities (analysis-core) and installed their successor "Warnings Next Generation" plugin and all works just fine now 

I strongly recommend to pay attention to Jenkins warnings about deprecated plugins and resolve them to avoid unexpected issues of this kind.

Hi,

I am also facing same issue , post update I am not able to save or apply under configurre system.

Current Jenkins version : Jenkins 2.289.2

All Available Plugins are updated .

jenkins-plugins-installed

amita0316 your list of plugins includes the aws-sqs plugin. It is listed in JENKINS-65834 as known to have issues with tables to divs. When I removed that plugin and disabled the azure-ad plugin, I was able to save the global configuration with your set of plugins.

Your list of plugins also includes the ruby runtime plugin. It should be removed as well, since it does not work with Java 11 and is planned to be deprecated soon.

label-linked-jobs caused our inability to save Jenkins Configuration.
https://issues.jenkins.io/browse/JENKINS-66115

Hi markewaite 

Thanks for the reply & it worked for me.

Thank you so much for your help.

Thanks & Regards

Amita

Hi,

I am also facing same issue , post update I am not able to save or apply under configure system.

Current Jenkins version : Jenkins 2.289.2

All Available Plugins are updated.

Below is the list of plugins currently installed - 
 
jenkins_plugins_installed.docx

atul1250 you said

All Available Plugins are updated.

yet I get the following output when I convert your list of plugins to plugins.txt format and run plugin installation manager tool

$ mkdir plugins
$ java -jar ../jenkins-plugin-manager-2.10.0.jar --jenkins-version 2.289.2 --latest false \
  --plugin-download-directory plugins --view-security-warnings  --plugin-file plugins.txt
generic-webhook-trigger (1.32): SECURITY-2330 XXE vulnerability https://www.jenkins.io/security/advisory/2021-06-18/#SECURITY-2330
kubernetes (1.12.8): SECURITY-1646 Jenkins controller environment variables accessible https://www.jenkins.io/security/advisory/2020-11-04/#SECURITY-1646
kubernetes (1.12.8): SECURITY-2102 Missing permission check allows listing pod templates https://www.jenkins.io/security/advisory/2020-11-04/#SECURITY-2102
kubernetes (1.12.8): SECURITY-2103 Missing permission check allows enumerating credentials IDs https://www.jenkins.io/security/advisory/2020-11-04/#SECURITY-2103
workflow-cps-global-lib (2.9): SECURITY-1422 Missing permission check https://jenkins.io/security/advisory/2019-07-31/#SECURITY-1422

Those plugins have security warnings. One of the steps in the 2.277.1 upgrade guide and webinar is to resolve all security warnings. In your case, you would do that by upgrading plugins.

In addition to those security warnings, there are many other plugins in your list that have not been upgraded.

I ran the command

$ java -jar ../jenkins-plugin-manager-2.10.0.jar --jenkins-version 2.289.2 \
  --plugin-download-directory plugins --plugin-file plugins.txt --no-download \
  --available-updates --output txt > x

and compared the output file x with the plugins.txt file that you provided. There are 114 plugins that need to be upgraded. When I upgraded those plugins and ran Jenkins 2.289.2, I was able to save the Jenkins configuration with "Configure system".

Thanks a ton markewaite for looking into this. Will upgrade all the plugins as mentioned as will share the results.

In our case we were able to narrow down the problem by applying the binary sort of disabling the plugins. 

In our test environment of jenkins 

i followed this approach. 

// code placeholder

cd $JENKINS_HOME/plugins/
// step 1
ls *.jpi|sort |egrep -v "workflow|pipeline|aws|cas-plugin"|grep -i  "^[a-j]"|while read line ; do  touch ${line}.disabled ; done
systemctl restart jenkins

// problem exists when opening the jenkins configure system end point.
// https://${jenkins-url}/configure and got error like below.
rm -rf [a-j]*.disabled

// step 2
ls *.jpi|sort |egrep -v "workflow|pipeline|aws|cas-plugin"|grep -i "^[f-j]"|while read line ; do touch ${line}.disabled ; done
systemctl restart jenkins

// problem exists when opening the jenkins configure system end point.
// https://${jenkins-url}/configure and got error like below.
rm -rf [f-j]*.disabled

// step 3
ls *.jpi|sort |egrep -v "workflow|pipeline|aws|cas-plugin"|grep -i "^[h-j]"|while read line ; do touch ${line}.disabled ; done 
systemctl restart jenkins 
// problem exists when opening the jenkins configure system end point. 
// https://${jenkins-url}/configure and got error like below.
rm -rf [f-j]*.disabled

// step 4 
ls *.jpi|sort |egrep -v "workflow|pipeline|aws|cas-plugin"|grep -i "^j"|while read line ; do touch ${line}.disabled ; done 
systemctl restart jenkins 
// problem exists when opening the jenkins configure system end point. 
// https://${jenkins-url}/configure and got error like below.


and finally i was able to identify when i disabled javadoc.jpi.disabled i was able to load the page normally.

and finally i was able to narrow down the plugin causing the issue for me when i disabled the plugin javadoc.    i was able to save the options in Jenkins > Configure System without any problem.  

kunaljha5 I'm not aware of any issue in the javadoc plugin related to tables to divs.

Did you follow the instructions in the 2.277.1 upgrade guide and upgrade your plugins to the latest versions? If you did and that still shows an issue in the javadoc plugin, please submit a separate issue for the javadoc plugin. Include precise details of the plugin versions installed on your system and the detailed steps you perform in order to see the problem.

Hi,

Recently i upgraded the jenkins to 2.319.1

After the upgrade whenever i go to any existing project to make some changes or ever for newly created project the save and apply is looking weird behind as shown in the picture.

I have also uploaded the list of plugins i am using.

Right now all the plugins are updated and no deprecated plugins are used.

I also tried and confirmed not using any of the affected plugins are discussed in this ticket.

jenkins_plugins_list

Any help will be appreciated..

rajivchirania the list that you uploaded includes the following plugins that are known to have issues with configuration form modernization:

• ivy - JENKINS-67449 - remove the ivy plugin and call ivy from a bat, powershell, or sh script

The list of plugins you have includes deprecated plugins:

• Multiple SCMs - remove the multiple SCMs plugin and use Jenkins Pipeline instead
• Azure Commons plugin - upgrade to latest Azure AD plugin in hopes of being able to remove this plugin

The list of plugins you have includes the following plugins with known security issues:

• Mercurial plugin 2.10 - upgrade to 2.16 or remove the plugin
• Azure AD plugin 1.2.0 - upgrade to at least 1.2.3
• Bitbucket approve plugin 1.0.3 - remove the plugin
• Role based authorization strategy 2.16 - upgrade to most recent release

Steps you should take:

• Remove the deprecated plugins (multiple SCMs)
• Remove the plugins that are known to not work with configuration forms modernization (Ivy)
• Upgrade all the plugins as instructed in the 2.277.1 upgrade guide

See the community.jenkins.io configuration form modernization summary for more details

Can we add Rundeck plugin too to the broken plugins dashboard? https://issues.jenkins.io/browse/JENKINS-65664

arunan done. I added the 'tables-to-divs-regression' label to that issue so that it is now visible in the list

Closing given no updates in 6 months

Hi,

Is this issue is resolved..? Because i also facing same issue in Jenkins 2.346.2 version, When i click Save and Apply button in ManageJenkins—>Manage and AssignRoles—>Save and Apply i'm getting "HTTP 403 No valid crumb was included in the request". Please help on this issue to fix.

degasuresh asking for help in a closed issue is much less likely to actually get help than if you ask in one of the locations that handle questions. Especially asking a question related to a different symptom than the specific issue where you are making your comment.

This issue is related to the transition of page layout from HTML table tags to HTML div tags. The issue you're describing is most likely not related to the page layout transition. However, in order to assure that the issue you are seeing is not related to the page layout transition, please follow all the steps described in https://community.jenkins.io/t/migrating-jenkins/894/5 . If you follow all those steps and still see the issue, you will increase the chances that others will be able to help you. You will also increase the chances that you'll solve the problem yourself.