-
Bug
-
Resolution: Cannot Reproduce
-
Blocker
-
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.
- is related to
-
JENKINS-73487 No such property: size for class: hudson.model.UpdateSite$Warning when using Java past version 11
-
- Closed
-
[JENKINS-72779] Scriplter 348.v5d461e205da_a_ not showing Scriptler navigation feature
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. |
Attachment | New: plugins.txt [ 62605 ] |
Attachment | New: run-jenkins.sh [ 62606 ] |
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 ] |
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 ] |
Resolution | New: Cannot Reproduce [ 5 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link |
New:
This issue is related to |