Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-49630

Unable to view configuration of some projects after upgrade to 2.107

      I upgraded Jenkins to 2.107 yesterday and upgraded all the plugins to their latest version. After that some of our jobs can no longer be configured. The page just shows "Loading" with a blinking icon. In addition, the chrome developer tool shows 

      hudson-behavior.js:424 Uncaught TypeError: Cannot read property 'firstChild' of undefined
      at registerValidator (hudson-behavior.js:424)
      at Array.forEach (<anonymous>)
      at behavior.js:111
      at Array.forEach (<anonymous>)
      at behavior.js:107
      at Array.forEach (<anonymous>)
      at Object.applySubtree (behavior.js:93)
      at select.js:269
      registerValidator @ hudson-behavior.js:424
      (anonymous) @ behavior.js:111
      (anonymous) @ behavior.js:107
      applySubtree @ behavior.js:93
      (anonymous) @ select.js:269
      setTimeout (async)
      (anonymous) @ select.js:263

          [JENKINS-49630] Unable to view configuration of some projects after upgrade to 2.107

          Rui Chen added a comment -

          "uninstalling Violations plugin" works for us (maven project loading issue is gone), we are using v2.113

          Rui Chen added a comment - "uninstalling Violations plugin" works for us (maven project loading issue is gone), we are using v2.113

          Marin Binzari added a comment -

          Same here with Jenkins 2.107.2. Desactivating the Violations plugin 0.7.11 (with dependencies on him Violation Columns(List View Columns) 1.6, Warnings Plug-in, Static Analysis Collector Plug-in 1.52) made possible editing the configuration of the project. Still getting JS errors in the browser console :

           

          hudson-behavior.js:424 Uncaught TypeError: Cannot read property 'firstChild' of undefined
              at registerValidator (hudson-behavior.js:424)
              at Array.forEach (<anonymous>)
              at behavior.js:111
              at Array.forEach (<anonymous>)
              at behavior.js:107
              at Array.forEach (<anonymous>)
              at Object.applySubtree (behavior.js:93)
              at select.js:269
          registerValidator	@	hudson-behavior.js:424
          (anonymous)	@	behavior.js:111
          (anonymous)	@	behavior.js:107
          applySubtree	@	behavior.js:93
          (anonymous)	@	select.js:269
          setTimeout (async)		
          (anonymous)	@	select.js:263
          
          
          
          
          configure:1 [DOM] Found 2 elements with non-unique id #svn.remote.loc: (More info: https://goo.gl/9p2vKq) input#svn.remote.loc.setting-input.validated input#svn.remote.loc.setting-input.validated
          
          
          
          
          hudson-behavior.js:1311 Unable to find nearby server
          (anonymous)	@	hudson-behavior.js:1311
          (anonymous)	@	prototype.js:853
          each	@	prototype.js:852
          refillOnChange	@	hudson-behavior.js:1308
          (anonymous)	@	select.js:77
          (anonymous)	@	behavior.js:111
          (anonymous)	@	behavior.js:107
          applySubtree	@	behavior.js:93
          apply	@	behavior.js:76
          (anonymous)	@	behavior.js:71
          window.onload	@	behavior.js:125

          Marin Binzari added a comment - Same here with Jenkins 2.107.2. Desactivating the Violations plugin 0.7.11 (with dependencies on him Violation Columns(List View Columns) 1.6, Warnings Plug-in, Static Analysis Collector Plug-in 1.52) made possible editing the configuration of the project. Still getting JS errors in the browser console :   hudson-behavior.js:424 Uncaught TypeError: Cannot read property 'firstChild' of undefined at registerValidator (hudson-behavior.js:424) at Array.forEach (<anonymous>) at behavior.js:111 at Array.forEach (<anonymous>) at behavior.js:107 at Array.forEach (<anonymous>) at Object .applySubtree (behavior.js:93) at select.js:269 registerValidator @ hudson-behavior.js:424 (anonymous) @ behavior.js:111 (anonymous) @ behavior.js:107 applySubtree @ behavior.js:93 (anonymous) @ select.js:269 setTimeout (async) (anonymous) @ select.js:263 configure:1 [DOM] Found 2 elements with non-unique id #svn.remote.loc: (More info: https: //goo.gl/9p2vKq) input#svn.remote.loc.setting-input.validated input#svn.remote.loc.setting-input.validated hudson-behavior.js:1311 Unable to find nearby server (anonymous) @ hudson-behavior.js:1311 (anonymous) @ prototype.js:853 each @ prototype.js:852 refillOnChange @ hudson-behavior.js:1308 (anonymous) @ select.js:77 (anonymous) @ behavior.js:111 (anonymous) @ behavior.js:107 applySubtree @ behavior.js:93 apply @ behavior.js:76 (anonymous) @ behavior.js:71 window.onload @ behavior.js:125

          Lambert Ma added a comment -

          Deactivating just Violations plugin 0.7.11 work for us.  Using Jenkins 2.107.2 LTS also.

          Lambert Ma added a comment - Deactivating just Violations plugin 0.7.11 work for us.  Using Jenkins 2.107.2 LTS also.

          Deactivating Violations plugin just works. Thank you

          Jorge Matricali added a comment - Deactivating Violations plugin just works. Thank you

          Mattsi Jansky added a comment -

          Having this issue on a brand new Jenkins ver. 2.138.1 instance with only the default suggested plugins, can't create a new build pipeline because of it. Don't have violations plugin. Can't remove the credentials plugin because everything (even git integration) is dependent on it.

          Mattsi Jansky added a comment - Having this issue on a brand new  Jenkins ver. 2.138.1  instance with only the default suggested plugins, can't create a new build pipeline because of it. Don't have violations plugin. Can't remove the credentials plugin because everything (even git integration) is dependent on it.

          Jesse Glick added a comment -

          This issue seems to have become a grab-bag of possibly many unrelated problems, without steps to reproduce. I would suggest closing it. Anyone encountering reproducible issues should please ignore this and file fresh issues with complete steps to reproduce from scratch.

          Jesse Glick added a comment - This issue seems to have become a grab-bag of possibly many unrelated problems, without steps to reproduce. I would suggest closing it. Anyone encountering reproducible issues should please ignore this and file fresh issues with complete steps to reproduce from scratch.

          I have this issue on new updated Jenkins (2.138.3). I can't create or open a Jenkins job with Maven type. It tries to load the config page and the loading symbol do not stop moving. If I remove the mentioned "violations" plugin, it works again. But I can't just remove the plugin. It will be needed for the code analysis I guess.

          Are there any news?

          Raphael Greger added a comment - I have this issue on new updated Jenkins (2.138.3). I can't create or open a Jenkins job with Maven type. It tries to load the config page and the loading symbol do not stop moving. If I remove the mentioned "violations" plugin, it works again. But I can't just remove the plugin. It will be needed for the code analysis I guess. Are there any news?

          Mattsi Jansky added a comment -

          In our case, we found that (for whatever reason) restarting the Jenkins instance fixed the issue.

          Mattsi Jansky added a comment - In our case, we found that (for whatever reason) restarting the Jenkins instance fixed the issue.

          Thank you for your answer, but in my case it do not solve the problem. I restarted Jenkins the last 3 days more than 20 times.

          Raphael Greger added a comment - Thank you for your answer, but in my case it do not solve the problem. I restarted Jenkins the last 3 days more than 20 times.

          As I read, the violations plugin will be replaced by the warnings plugin. So I removed the violations plugin and my Jenkins is now running without problem.

          Raphael Greger added a comment - As I read, the violations plugin will be replaced by the warnings plugin. So I removed the violations plugin and my Jenkins is now running without problem.

            Unassigned Unassigned
            rgoers Ralph Goers
            Votes:
            12 Vote for this issue
            Watchers:
            33 Start watching this issue

              Created:
              Updated:
              Resolved: