Similar to Randall (the.n...), I have customers that use NonStop, but they also use various distros of Enterprise Linux. Their corporate strategy for software development is to remain on Java 8 for the foreseeable future, primarily due to the JDK 11 licensing mentioned above. They have a corporate support contract with Oracle to continue to get Java 8 updates, so support is not an issue for them. Shipping a version of Jenkins that won't do 'remoting' on those target platforms should require much longer than 5 months of advance notice, as those customers are on much longer strategic cycles.
Even though the newer platforms and releases for NonStop include both Java 8 and Java 11, customers on NonStop and Linux that are Enterprise-focused (and there are MANY) haven't installed Java 11 and have no plan to do so this year or probably even next. What was the penetration number above for Java 11, only 4%? Expecting a large percentage of your customer base to make this move is short-sighted. If Jenkins is to retain its preferred position in Enterprise environments, this decision should be very carefully reconsidered. Most of your customers don't spend time reviewing this group. And many Enterprise decisionmakers don't participate in Twitter, which leaves the results of surveys in that platform somewhat questionable. This is not just a question of what is easier for the developers of Jenkins, it's also a matter of where Jenkins (and its remotes) run. This is just my .02$US, On Wednesday, August 4, 2021 at 2:11:30 PM UTC-5 [email protected] wrote: > That's assuming that Docker runs on NonStop, which it doesn't. The key > issue is remoting.jar and whether that can be maintained at 1.8 > compatibility. Most groups are using a Controller/Agent architecture using > Docker for the Controller and running the platform JVM for remoting.jar. > There are a few using the jenkins.war, so as long as that is also 1.8 > compatible, building using 11 is fine. > > On Wednesday, August 4, 2021 at 2:55:02 p.m. UTC-4 Jesse Glick wrote: > >> On Wed, Aug 4, 2021 at 2:13 PM Randall Becker <[email protected]> wrote: >> >>> when deploying Jenkins into production environments […] using the Oracle >>> JRE is a requirement not an option >>> >> >> If your environment has specialized needs, including legal ones, you can >> of course build your own Docker images accordingly starting with a WAR >> file. The question is about the default images supported by the Jenkins >> project and deemed suitable for typical purposes. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/0cf24bed-2fd3-49e9-9c7e-aebd4bbba23dn%40googlegroups.com.
