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

Scriplter 348.v5d461e205da_a_ not showing Scriptler navigation feature

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • scriptler-plugin
    • Jenkins 2.440.1 on Windows/Apache Tomcat 9, tested with Java versions 11,17 and 21, chrome

      Version 348.v5d461e205da_a_ proves to be very difficult to install without stopping the Jenkins start-up.  Once all latest versions of the dependencies were also correct, Jenkins would successfully start, which is fair I guess.

      Regardless, this version soon 'oops/devils' the Manage Jenkins page, forcing a Jenkins restart.

      However, after significant testing, the above problems seem related to Java version past 11.

      Ultimately rolling back to Java 11, it was found that the Scriptler menu item on the bottom of the left navigation pane was missing.  Also, trying to go to the url manually reported unauthorized.

      We rolled back one version of Scriptler and functionality appears correct.

      Dissatisfied with the java version limitation.

          [JENKINS-72779] Scriplter 348.v5d461e205da_a_ not showing Scriptler navigation feature

          Mark Waite added a comment - - edited

          teaflood01 I am unable to duplicate the problem as described. As far as I can tell, the Scriptler plugin is behaving correctly on Java 11 and on Java 21. Steps that I took while trying to duplicate the problem included:

          1. Create a plugins.txt file that lists the plugins and their versions to install
          2. Create a run-jenkins.sh shell script that downloads Jenkins 2.440.1 and the plugins listed in the plugins.txt file
          3. Run the run-jenkins.sh shell script and complete the setup wizard by choosing to install no additional plugins and by creating a new user
          4. Open Scriptler from "Manage Jenkins" and define a new script that runs "println System.getenv("PATH")"
          5. Open "In-process Script Approval" from "Manage Jenkins" and approve the newly added script
          6. Open Scriptler from "Manage Jenkins" and run the script, confirm that it provides the expected output

          I performed those actions with Java 11.0.23 and with Java 21.0.3 on my Debian computer and found no differences in behavior between Java 11 and Java 21.

          Can you provide more details so that others can duplicate the issue?

          I intentionally did not attempt to use Apache Tomcat 9 in my testing because the Jenkins servlet container support policy notes that Apache Tomcat 9 is a level 2 option while the Winstone container that is included in Jenkins is a level 1 option. You might try running Jenkins without Apache Tomcat to see if that shows different behavior in your case.

          Mark Waite added a comment - - edited teaflood01 I am unable to duplicate the problem as described. As far as I can tell, the Scriptler plugin is behaving correctly on Java 11 and on Java 21. Steps that I took while trying to duplicate the problem included: Create a plugins.txt file that lists the plugins and their versions to install Create a run-jenkins.sh shell script that downloads Jenkins 2.440.1 and the plugins listed in the plugins.txt file Run the run-jenkins.sh shell script and complete the setup wizard by choosing to install no additional plugins and by creating a new user Open Scriptler from "Manage Jenkins" and define a new script that runs "println System.getenv("PATH")" Open "In-process Script Approval" from "Manage Jenkins" and approve the newly added script Open Scriptler from "Manage Jenkins" and run the script, confirm that it provides the expected output I performed those actions with Java 11.0.23 and with Java 21.0.3 on my Debian computer and found no differences in behavior between Java 11 and Java 21. Can you provide more details so that others can duplicate the issue? I intentionally did not attempt to use Apache Tomcat 9 in my testing because the Jenkins servlet container support policy notes that Apache Tomcat 9 is a level 2 option while the Winstone container that is included in Jenkins is a level 1 option. You might try running Jenkins without Apache Tomcat to see if that shows different behavior in your case.

          Mark Waite added a comment -

          Closing as "Cannot reproduce" after a week without a response.

          Mark Waite added a comment - Closing as "Cannot reproduce" after a week without a response.

            Unassigned Unassigned
            teaflood01 Tod
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: