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

          Tod created issue -
          Tod made changes -
          Description Original: 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/devlis' 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 and functionality appears correct.

          Dissatisfied with the java version limitation.
          New: 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.
          Mark Waite made changes -
          Attachment New: plugins.txt [ 62605 ]
          Mark Waite made changes -
          Attachment New: run-jenkins.sh [ 62606 ]

          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 made changes -
          Comment [ Hello, [~teaflood01] 

          It seems you’ve encountered a series of issues with the Scriptler plugin version 348.v5d461e205da_a_ and Jenkins, particularly related to Java versions newer than 11. The problems you’ve described, such as the ‘oops/devils’ error on the Manage Jenkins page and the missing Scriptler menu item, are indicative of compatibility issues between the plugin, Jenkins, and the Java version. {color:#c1c7d0}[aarp-mahjongg.com|https://www.aarp-mahjongg.com]{color}

          Rolling back to an earlier version of Scriptler restored functionality, which suggests that the latest version of the plugin may not be fully compatible with newer Java versions. This is not uncommon, as plugins can lag behind in support for newer versions of their dependencies.

          Here are some steps you can consider:

          Check Compatibility: Ensure that the Scriptler plugin and all its dependencies are compatible with the Java version you are using. The Jenkins community often documents such compatibility issues, and you can find more information on the Scriptler plugin page or the Jenkins plugin documentation.
          Review Plugin Updates: Look for any recent updates or patches for the Scriptler plugin that might address these issues. Sometimes, plugin developers release quick fixes following the discovery of bugs or compatibility problems.
          Community Support: If the issue persists, consider reaching out to the Jenkins community for support. You can report the issue on the Scriptler GitHub repository or seek advice on forums like Stack Overflow.
          Java Version: If you must use a newer version of Java for other dependencies, you might need to wait for the Scriptler plugin to update its compatibility or explore alternative plugins that offer similar functionality.

           

           

          Best Regard,
          patrick521f ]
          Mark Waite made changes -
          Comment [ [~patrick521f] that response looks like it was created with a chatbot using generative AI. Is that how it was generated? Did you attempt to duplicate the problem or were you just attempting to provide general purpose advice?

          You listed several possible actions, but don't seem to have taken those actions yourself. Is that intentional?

          bq. Check compatibility

          There are no references to any incompatibility between the Scriptler plugin and newer Java versions in any of the [open issues|https://issues.jenkins.io/issues/?jql=resolution%20is%20EMPTY%20and%20component%3D15743]

          bq. Review Plugin Updates

          The 348.v5d461e205da_a_ release is the [most recent release|https://plugins.jenkins.io/scriptler/releases/].

          bq. Community Support

          You mentioned that issues could be reported to the GitHub repository, yet the ["report an issue" link|https://www.jenkins.io/participate/report-issue/redirect/#15743] on the [plugin page|https://plugins.jenkins.io/scriptler/] goes to Jenkins Jira, not to the GitHub repository ]

          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.
          Mark Waite made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Mark Waite made changes -
          Link New: This issue is related to JENKINS-73487 [ JENKINS-73487 ]

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

              Created:
              Updated:
              Resolved: