Hi Bob, we also have legacy projects where developers still need Java 1.6. But maybe there is a misunderstanding, you don't need to run Jenkins istself under that version then, even not the agents. You just need to have a JDK1.6 somewhere available on your agent and configred as tool for your agent, then select this JDK in the build job/pipeline script.
Harald [email protected] schrieb am Dienstag, 13. Juli 2021 um 20:27:59 UTC+2: > I downgraded script-security to a version that runs in 1.6 and the problem > is now fixed. Thanks for your help! > > On Monday, July 12, 2021 at 10:11:03 PM UTC+3 [email protected] wrote: > >> I guess you update some plugins one of those plugins is the script >> security plugin, which in the version you update works on Jenkins 1.609 but >> does not support Java 6. I will tell you that the faster solution is to >> restore the plugins folder from a backup that you have before the changes >> on the plugins, if you do not have that backup you have to review all hpi >> files in the plugins folder, and check the file MANIFEST.MF inside the hip >> file, it is a zip, in that manifest, you have to check the value in >> "Minimum-Java-Version:", all the plugins that require 1.8 are not valid for >> your installation. But again you have a security clock boom on that >> instance a Java version from 2013 and a Jenkins core from 2015. >> >> El lunes, 12 de julio de 2021 a las 20:21:51 UTC+2, [email protected] >> escribió: >> >>> On our current production server we run 1.609 with Java 1.6. It is very >>> very old but it's not my decision to upgrade it, it's the Dev Team's. This >>> version and this Java are indeed compatible, Jenkins runs fine on our >>> current server. >>> >>> I therefore need to revert to 1.6 anything that has, inadvertently, gone >>> to 1.8. Please help me with that. To start with, am I running into 1.8 >>> plugins, or 1.8 artifacts? >>> >>> Some sites suggest that this is a browser/Javascript issue. I'm at a >>> loss. >>> >>> On Monday, July 12, 2021 at 7:25:52 PM UTC+3 [email protected] wrote: >>> >>>> "Unsupported major.minor version 52.0" means that you need to run on >>>> Java 8 (see >>>> https://stackoverflow.com/questions/10382929/how-to-fix-java-lang-unsupportedclassversionerror-unsupported-major-minor-versi/ >>>> ) >>>> >>>> the Java 6 version you are using is EOL since 2013 (see >>>> https://en.wikipedia.org/wiki/Java_version_history) and your Jenkins >>>> version was released in 2015 (see >>>> https://www.jenkins.io/changelog-stable/#v1.609.3) so I don't know if >>>> that version can run on Java 6, I dunno why you are trying to use >>>> something >>>> old and with tons of issues resolved in the latest version on an outdated >>>> and without support Java version, but sounds like a no-good idea. >>>> >>>> El lunes, 12 de julio de 2021 a las 16:33:20 UTC+2, [email protected] >>>> escribió: >>>> >>>>> Let me add that the system property java.class.version on both >>>>> servers new (source and copy) has the value 50.0 >>>>> >>>>> So it seems I need to get rid of all 52.0 stuff. >>>>> >>>>> >>>>> >>>>> On Monday, July 12, 2021 at 4:30:53 PM UTC+3 GI D wrote: >>>>> >>>>>> On a copied installation of Jenkins 1.609 to a new server, I notice >>>>>> that when I select a build and click "configure", I get a greyed-out >>>>>> config >>>>>> page with "LOADING" as a watermark that never goes away. At the same >>>>>> time I >>>>>> see in catalina.out lots of errors such as this: >>>>>> >>>>>> Jul 12, 2021 4:15:20 PM hudson.ExpressionFactory2$JexlExpression >>>>>> evaluate >>>>>> WARNING: Caught exception evaluating: d.helpFile in >>>>>> /jenkins/job/platform%20set%20branch%20name/configure. Reason: jav >>>>>> a.lang.reflect.InvocationTargetException >>>>>> .... >>>>>> .... >>>>>> Caused by: java.lang.UnsupportedClassVersionError: >>>>>> org/jenkinsci/plugins/scriptsecurity/sandbox/RejectedAccessException : >>>>>> Unsupported major.minor version 52.0 >>>>>> >>>>>> I think the reason is that, for a few days, I was running the new >>>>>> Jenkins with a slightly newer Java version (1.6.0_41 rather than >>>>>> 1.6.0_30). >>>>>> Now I have made sure I run it with _30. During this short period this >>>>>> particular build has been executed a few times. However I do get the >>>>>> same >>>>>> problem on other builds that have not executed on this new server. >>>>>> >>>>>> Almost all errors (or warnings if you will) are about the >>>>>> script-security plugin. >>>>>> >>>>>> Please advise. >>>>>> >>>>>> - George >>>>>> >>>>>> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/071b6729-2d51-4d21-89d5-e38d1bb3d8acn%40googlegroups.com.
