• Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • core
    • Windows v.2.105

      Hello, 

      We have a problem to access to configure page of a job because of a js exception : 

      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

      So it always refresh.

          [JENKINS-49375] Cannot read property 'firstChild' of undefined

          Oleg Nenashev added a comment -

          Please reopen the page in the Javascript debugger and report, for which item select.js gets invoked with failure. It will help to triage the plugin

          Oleg Nenashev added a comment - Please reopen the page in the Javascript debugger and report, for which item select.js gets invoked with failure. It will help to triage the plugin

          Daniel Beck added a comment -

          Any number of plugins can cause this problem.

          The problem is that it's also possibly unique to your instance configuration, not even matching plugins exactly may help.

          Please try to figure out the minimal set of plugins needed, and configuration set, to reproduce this issue on a pristine instance from scratch. Only then is there a chance for us to fix it.

          Daniel Beck added a comment - Any number of plugins can cause this problem. The problem is that it's also possibly unique to your instance configuration, not even matching plugins exactly may help. Please try to figure out the minimal set of plugins needed, and configuration set, to reproduce this issue on a pristine instance from scratch. Only then is there a chance for us to fix it.

          thomas cornez added a comment - - edited

          Every pluggin are update exept Maven Integration plugin which is still in version 2.17 because one of our project is incompatible.

          May it be the problem?

          Even when we create a new job we have the same issue. Only some job which only make our deployement (some ssh command) can be configure.

          thomas cornez added a comment - - edited Every pluggin are update exept  Maven Integration plugin  which is still in version 2.17 because one of our project is incompatible. May it be the problem? Even when we create a new job we have the same issue. Only some job which only make our deployement (some ssh command) can be configure.

          Rui Chen added a comment -

          This is a very frustrating issue causing us rollback Jenkins from v2.105 to v2.104. 

          However in v2.105, all the XML config files are tagged with v1.1 instead of v1.0 as below:

          {code}

          Caused by: org.xmlpull.v1.XmlPullParserException: only 1.0 is supported as <?xml version not '1.1' (position: START_DOCUMENT seen <?xml version=\'1.1\'... @1:19)
          at org.xmlpull.mxp1.MXParser.parseXmlDeclWithVersion(MXParser.java:2608)

          {code}

           

          I wonder if anyone has fix for the above issue. Thanks.

          Rui Chen added a comment - This is a very frustrating issue causing us rollback Jenkins from v2.105 to v2.104.  However in v2.105, all the XML config files are tagged with v1.1 instead of v1.0 as below: {code} Caused by: org.xmlpull.v1.XmlPullParserException: only 1.0 is supported as <?xml version not '1.1' (position: START_DOCUMENT seen <?xml version=\'1.1\'... @1:19) at org.xmlpull.mxp1.MXParser.parseXmlDeclWithVersion(MXParser.java:2608) {code}   I wonder if anyone has fix for the above issue. Thanks.

          chenrui like Daniel said above, if you are able to create a minimum case reproducer, this would be most welcome. As for now, that issue has been closed as "Cannot Reproduce".

          And reading above, I can't see anything that would link to the maven-integration plugin, apart from that previous comment about its version and yours following, so again please if you wish to see this fixed, please provide the necessary data.

          (Apart from that, you will probably be interested to know that many of us consider the maven-integration plugin as de-facto deprecated.)

          Baptiste Mathus added a comment - chenrui like Daniel said above, if you are able to create a minimum case reproducer, this would be most welcome. As for now, that issue has been closed as "Cannot Reproduce". And reading above, I can't see anything  that would link to the maven-integration plugin, apart from that previous comment about its version and yours following, so again please if you wish to see this fixed, please provide the necessary data. (Apart from that, you will probably be interested to know that many of us consider the maven-integration plugin  as de-facto deprecated.)

          Rui Chen added a comment -

          batmat yes, that is good to know that maven project support got deprecated.

          I think our config loading issue is around there.

          Rui Chen added a comment - batmat yes, that is good to know that maven project support got deprecated. I think our config loading issue is around there.

          Rui Chen added a comment -

          batmat Do you have any documentation reference about migrating the jenkins maven projects?

          Thanks,
          Rui

          Rui Chen added a comment - batmat Do you have any documentation reference about migrating the jenkins maven projects? Thanks, Rui

          thomas cornez added a comment -

          How can we provide those necessary data?

          Do you want a config.xml from a project that has the problem?

          thomas cornez added a comment - How can we provide those necessary data? Do you want a config.xml from a project that has the problem?

          Daniel Beck added a comment - - edited

          chenrui  Not really deprecated, we just know it's terrible, and have known for a long time. For example, you'll see references to http://javaadventure.blogspot.de/2013/11/jenkins-maven-job-type-considered-evil.html written by a Maven committer on the Jenkins team occasionally. (batmat Or did I miss something?) For that reason, use is generally discouraged, but given how plugin dependencies work, it's just there on most instances. And since it's both convenient and does things no other plugin does, people continue using it. I don't think the Pipeline Maven Plugin is quite there yet.

          theljade config.xml might help, but not certain. Ideally you'll start Jenkins with an empty JENKINS_HOME. Do whatever is needed to make this issue appear, and take notes. If it's as easy as installing the plugins you have installed and dumping the job config.xml there so Jenkins loads it, that would be pretty straightforward. Then, do it again until you get streamlined steps to reproduce from scratch. Like Stack Overflow asking for minimal code samples, we're asking for minimal steps to reproduce. Less work and less errorprone that way.

          Daniel Beck added a comment - - edited chenrui   Not really deprecated, we just know it's terrible, and have known for a long time. For example, you'll see references to http://javaadventure.blogspot.de/2013/11/jenkins-maven-job-type-considered-evil.html written by a Maven committer on the Jenkins team occasionally. ( batmat Or did I miss something?) For that reason, use is generally discouraged, but given how plugin dependencies work, it's just there on most instances. And since it's both convenient and does things no other plugin does, people continue using it. I don't think the Pipeline Maven Plugin is quite there yet. theljade config.xml might help, but not certain. Ideally you'll start Jenkins with an empty JENKINS_HOME. Do whatever is needed to make this issue appear, and take notes. If it's as easy as installing the plugins you have installed and dumping the job config.xml there so Jenkins loads it, that would be pretty straightforward. Then, do it again until you get streamlined steps to reproduce from scratch. Like Stack Overflow asking for minimal code samples, we're asking for minimal steps to reproduce. Less work and less errorprone that way.

          Rui Chen added a comment -

          Thanks danielbeck, the link is pretty helpful.

          Do you have any reference links for pipeline maven plugin as well?

          Rui Chen added a comment - Thanks danielbeck , the link is pretty helpful. Do you have any reference links for pipeline maven plugin as well?

            Unassigned Unassigned
            theljade thomas cornez
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: