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

TypeError: Cannot read property 'hasClassName' of undefined

    XMLWordPrintable

Details

    Description

      Attempting to click "Apply" and "Save" in any new project configuration page, nothing happens. Confirmed in Chrome dev tools this is the same behavior on any system, any web browser.

      behavior.js:119 TypeError: Cannot read property 'hasClassName' of undefined
    at hudson-behavior.js:1188
    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)

      Unable to add new projects or make changes to existing ones in both Multibranch pipeline projects and Github Organization projects.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          markewaite Mark Waite added a comment -

          chamoisla this is likely due to the configuration form modernization that was released in Jenkins 2.277.1. Unfortunately, the information you provided is not enough for others to assist you.

          Steps you can take to help yourself and help others help you

          • Follow the instructions in the Jenkins 2.277.1 upgrade guide and the Jenkins 2.277.1 webinar (and its slides)
            • Remove unused plugins from your installation
            • Remove plugins with security issues from your installation (like the TFS plugin)
            • Remove deprecated plugins from your installation (like the DRY plugin, the checkstyle plugin, the warnings plugin, etc.)
            • Update plugins to the latest releases
          • Confirm that the issue is still visible
          • Provide the information requested in "How to report an issue", especially including the specific details :
            • Jenkins version
            • Jenkins plugin names and versions (please report with the format provided by the script)
          markewaite Mark Waite added a comment - chamoisla this is likely due to the configuration form modernization that was released in Jenkins 2.277.1 . Unfortunately, the information you provided is not enough for others to assist you. Steps you can take to help yourself and help others help you Follow the instructions in the Jenkins 2.277.1 upgrade guide and the Jenkins 2.277.1 webinar (and its slides ) Remove unused plugins from your installation Remove plugins with security issues from your installation (like the TFS plugin) Remove deprecated plugins from your installation (like the DRY plugin, the checkstyle plugin, the warnings plugin, etc.) Update plugins to the latest releases Confirm that the issue is still visible Provide the information requested in "How to report an issue" , especially including the specific details : Jenkins version Jenkins plugin names and versions (please report with the format provided by the script )
          chamoisla Lauren added a comment -

          I fixed this by reinstalling Branch API plugin.

          chamoisla Lauren added a comment - I fixed this by reinstalling Branch API plugin.

          People

            chamoisla Lauren
            chamoisla Lauren
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: