So another idea that “update button” should compare and warn about java versions if they planned to be changed :)
> On Mar 25, 2015, at 00:03, Christopher Orr <[email protected]> wrote: > > I don't actually know how the startup / WAR extraction stuff works, but I did > wonder whether a Java 6-compatible piece of code could be run at startup to > print a "Jenkins now requires Java 8" warning to the console. > > But in any case, we need to warn users well in advance of upgrading. A lot > of people won't be happy if they hit the upgrade button in the UI only to > find that Jenkins doesn't come up again. > > > On 24/03/15 13:51, Kanstantsin Shautsou wrote: >> I think jenkins can check java version on startup and print friendly message >> to log instead of some java related stacktraces. >> >>> On Mar 24, 2015, at 23:46, Christopher Orr <[email protected]> wrote: >>> >>> Yeah, since we're upgrading, it may as well be to Java 8 since it (seems to >>> be) be available for every OS we package for, and it would minimise the >>> pain for users, rather than splitting it across two updates. >>> >>> I don't think we specify the required Java version in most of our native >>> package specs, and WAR users upgrading will have no way of knowing about >>> the Java requirement change, so we probably need to do a lot of user >>> education in advance. >>> >>> Maybe we can have banners inside the web interface for one or two releases >>> in advance, warning about the impending Java version requirement? Plus big >>> red text in the changelog, articles on the blog, Twitter etc. >>> >>> Some banners on the website, wiki and issue tracker (as we sometimes do, >>> e.g. for donation or JUC advertising) would also be a good idea. >>> >>> Regards, >>> Chris >>> >>> >>> On 24/09/14 12:40, Baptiste Mathus wrote: >>>> I'm absolutely +1 on the advantages on the programming model that >>>> defining a JDK8 as a minimum JDK would give us. And like Nicolas, I also >>>> think JDK7 is not really worth it as 8 is. >>>> >>>> And Jenkins is one of those tools that has somehow a lower barrier on >>>> that requirement upgrade, since for example the build JDK can a totally >>>> different one, or wouldn't impact say a ruby/C/whatever compiler anyway. >>>> >>>> Btw, I guess we own at least of those AIX installs, and JDK are actually >>>> generally not so that behind. JDK8 for AIX seems to be not GA *yet* but >>>> I'm sure IBM is working on it if not already out (found >>>> http://www.ibm.com/developerworks/java/jdk/beta/ for example). >>>> Sure, old platform like AIX 4 or 5.x wouldn't have those JDK supported, >>>> so I suppose there could be some Jenkins VeryLTS to keep Java 6 as it's >>>> now for say some months or even a year for only very important issues. >>>> That would give time for those platform a bit more time to provide the >>>> JDK8 port/version for their OS. >>>> >>>> 2014-09-24 19:42 GMT+02:00 Daniel Beck <[email protected] >>>> <mailto:[email protected]>>: >>>> >>>> >>>> On 24.09.2014, at 11:48, Martin Kutter <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> >>>> > Just want to throw in that java 8 is not yet available on all >>>> platforms >>>> > (like AIX, HP-UX and probably some other less frequently used >>>> commercial >>>> > UNIXes). >>>> >>>> I checked the anonymous usage stats a few weeks ago: >>>> Out of 93,400 installs, we know the master's OS for 85,200 of them. >>>> 285 are AIX. 120 are HP-UX. 50 installs total on OpenBSD, Darwin, >>>> OS/400, z/OS and NetBSD. >>>> >>>> Not relevant enough IMO if the advantages are significant. >>>> >>>> I can provide the queries I used if anyone wants to verify these. >>>> >>>> -- >>>> 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] >>>> <mailto:jenkinsci-dev%[email protected]>. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> -- >>>> Baptiste <Batmat> MATHUS - http://batmat.net >>>> Sauvez un arbre, >>>> Mangez un castor ! nbsp;! >>>> >>>> -- >>>> 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] >>>> <mailto:[email protected]>. >>>> For more options, visit https://groups.google.com/d/optout. >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Jenkins Developers" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/jenkinsci-dev/sw_WepGw0Pk/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/5511CD16.6090302%40orr.me.uk. >>> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/sw_WepGw0Pk/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/5511D127.90609%40orr.me.uk. > For more options, visit https://groups.google.com/d/optout. -- 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/60304202-5AA7-43C3-83F4-828AC1ED9997%40gmail.com. For more options, visit https://groups.google.com/d/optout.
