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

No such property: size for class: hudson.model.UpdateSite$Warning when using Java past version 11

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • jenkins versions past 2.442 and java past version 11, that is, this anything past this combination causes the error
    • 2.488, 2.479.3

      With any version of the scriplter plugin installed in a jenkins version greater than 2.442 or a java version past 11, the jenkins interface crashes with the log entry of:

      org.apache.commons.jelly.JellyTagException: jar:file:/D:/Apps/Tomcat%209.0/webapps/jenkins/WEB-INF/lib/jenkins-core-2.452.3.jar!/hudson/model/ManageJenkinsAction/index.jelly:45:57: <st:include> Exception evaluating property 'size' for java.util.ArrayList, Reason: groovy.lang.MissingPropertyException: No such property: size for class: hudson.model.UpdateSite$Warning at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:719)

          [JENKINS-73487] No such property: size for class: hudson.model.UpdateSite$Warning when using Java past version 11

          Mark Waite added a comment - - edited

          I'm unable to duplicate the problem as described. The issue may be somehow related to your use of Tomcat as a container instead of using the Jenkins Winstone container. It could be related to some other setting. It could be related to the plugins you have installed compared to the plugins that I have installed.

          You'll need to provide more details so that others can duplicate the issue that you are seeing. "How to report an issue" describes the types of details that are needed.

          Steps that I took while trying to duplicate the issue:

          1. Create a plugins.txt file that lists the plugins I've installed, included the suggested plugins from the Setup Wizard and scriptler plugin 363.vd97ef616cb_f9
          2. Create a run-jenkins.sh shell script that downloads Jenkins 2.468 and the plugins defined in the plugins.txt file
          3. Run the run-jenkins.sh shell script and complete the setup wizard by installing no additional plugins and creating a user
          4. Define a script println System.getenv("PATH") with the scriptler menu and save it
          5. Run the script and confirm that the system refuses to run the script because it has not yet been approved
          6. Use the script approval page from "Manage Jenkins" to approve the script
          7. Run the script and confirm that the script runs and generates the expected output
          8. Confirm that no warning messages were printed to the console where the run-jenkins.sh shell script is running

          The steps were run with Java 21.0.4 on a Debian Linux computer.

          Mark Waite added a comment - - edited I'm unable to duplicate the problem as described. The issue may be somehow related to your use of Tomcat as a container instead of using the Jenkins Winstone container. It could be related to some other setting. It could be related to the plugins you have installed compared to the plugins that I have installed. You'll need to provide more details so that others can duplicate the issue that you are seeing. "How to report an issue" describes the types of details that are needed. Steps that I took while trying to duplicate the issue: Create a plugins.txt file that lists the plugins I've installed, included the suggested plugins from the Setup Wizard and scriptler plugin 363.vd97ef616cb_f9 Create a run-jenkins.sh shell script that downloads Jenkins 2.468 and the plugins defined in the plugins.txt file Run the run-jenkins.sh shell script and complete the setup wizard by installing no additional plugins and creating a user Define a script println System.getenv("PATH") with the scriptler menu and save it Run the script and confirm that the system refuses to run the script because it has not yet been approved Use the script approval page from "Manage Jenkins" to approve the script Run the script and confirm that the script runs and generates the expected output Confirm that no warning messages were printed to the console where the run-jenkins.sh shell script is running The steps were run with Java 21.0.4 on a Debian Linux computer.

          Mark Waite added a comment -

          This report looks very similar to a report from earlier this year that received no response and could not be duplicated.  teaflood if you want further action on this, you'll need to provide enough information so that others can duplicate it.

          Does the failure only happen when Tomcat is used and not when the Jenkins Winstone container is used?

          What plugins are you using and what are their versions?

          Mark Waite added a comment - This report looks very similar to a report from earlier this year that received no response and could not be duplicated.   teaflood  if you want further action on this, you'll need to provide enough information so that others can duplicate it. Does the failure only happen when Tomcat is used and not when the Jenkins Winstone container is used? What plugins are you using and what are their versions?

          Mark Waite added a comment -

          Closing as "Cannot reproduce" after 2 months without a response to the request for more information.

          Mark Waite added a comment - Closing as "Cannot reproduce" after 2 months without a response to the request for more information.

            danielbeck Daniel Beck
            teaflood Tod
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: