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

Unable to view configuration of some projects after upgrade to 2.107

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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

        Attachments

          Issue Links

            Activity

            Hide
            mjansky 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.

            Show
            mjansky 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.
            Hide
            jglick 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.

            Show
            jglick 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.
            Hide
            rag1 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?

            Show
            rag1 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?
            Hide
            mjansky Mattsi Jansky added a comment -

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

            Show
            mjansky Mattsi Jansky added a comment - In our case, we found that (for whatever reason) restarting the Jenkins instance fixed the issue.
            Hide
            rag1 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.

            Show
            rag1 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.

              People

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

                Dates

                • Created:
                  Updated: