Re: [INFRA-2086] - Switching ci.jenkins.io builds to AdoptOpenJDK

On Fri, May 3, 2019 at 4:37 AM Robert Sandell wrote: > If I read the migration guide on the AdoptOpenJDK correctly it states that > there is no Java Web start replacement for Java 8. don't we have some Java > Web Start code at least in core for agent launching? Yes, but this is gone in newer

Re: [INFRA-2086] - Switching ci.jenkins.io builds to AdoptOpenJDK

Hi, We do not use Java Web Start in the Jenkins infrastructure. Indeed it may become an issue for some users who want to fully migrate to AdoptOpenJDK and who connect agents from WebUI, but it would not be a big issue for us even if we decided to change the base image for our official Jenkins

Re: [INFRA-2086] - Switching ci.jenkins.io builds to AdoptOpenJDK

If I read the migration guide on the AdoptOpenJDK correctly it states that there is no Java Web start replacement for Java 8. don't we have some Java Web Start code at least in core for agent launching? Or maybe that's not a compile time dependency? /B Den fre 3 maj 2019 kl 08:36 skrev Joseph P

[INFRA-2086] - Switching ci.jenkins.io builds to AdoptOpenJDK

Sounds perfectly reasonable to me  We use AdoptOpenJDK at work too. -- 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

Re: [INFRA-2086] - Switching ci.jenkins.io builds to AdoptOpenJDK

I'm also +1 for AdoptOpenJDK. Agreed with the GitHub caveats as well. On Thu, May 2, 2019 at 9:02 AM Oleg Nenashev wrote: > > By the way, we do caching on the agent level. > Windows agents are not single-shot ones, and download happens only once per > agent provisioning. > So it is not that bad

Re: [INFRA-2086] - Switching ci.jenkins.io builds to AdoptOpenJDK

By the way, we do caching on the agent level. Windows agents are not single-shot ones, and download happens only once per agent provisioning. So it is not that bad at one may expect On Thursday, May 2, 2019 at 3:56:01 PM UTC+2, R. Tyler Croy wrote: > > (replies inline) > > On Thu, 02 May 2019,

Re: [INFRA-2086] - Switching ci.jenkins.io builds to AdoptOpenJDK

(replies inline) On Thu, 02 May 2019, Jesse Glick wrote: > On Thu, May 2, 2019 at 9:12 AM Oleg Nenashev wrote: > > The releases are distributed from GitHub, so they are more stable even if > > we continue downloading JDKs by URL. > > It ought to be easy to configure the (nginx?) mirror

Re: [INFRA-2086] - Switching ci.jenkins.io builds to AdoptOpenJDK

On Thu, May 2, 2019 at 9:12 AM Oleg Nenashev wrote: > The releases are distributed from GitHub, so they are more stable even if we > continue downloading JDKs by URL. It ought to be easy to configure the (nginx?) mirror running in Azure for use by ci.jenkins.io builds to also mirror

Re: [INFRA-2086] - Switching ci.jenkins.io builds to AdoptOpenJDK

+1 from me. On Thu, May 2, 2019 at 7:14 AM Slide wrote: > +1 from me on this, I have switched to AdoptOpenJDK at work for pretty > much everything and it seems to work great. > > On Thu, May 2, 2019 at 6:12 AM Oleg Nenashev > wrote: > >> Hi all, >> >> As you may have noticed, last weekend many

Re: [INFRA-2086] - Switching ci.jenkins.io builds to AdoptOpenJDK

+1 from me on this, I have switched to AdoptOpenJDK at work for pretty much everything and it seems to work great. On Thu, May 2, 2019 at 6:12 AM Oleg Nenashev wrote: > Hi all, > > As you may have noticed, last weekend many CI jobs in the core and plugins > were failing due to the

[INFRA-2086] - Switching ci.jenkins.io builds to AdoptOpenJDK

Hi all, As you may have noticed, last weekend many CI jobs in the core and plugins were failing due to the unavailability of OpenJDK downloads from https://download.java.net (see INFRA-2086 ). After the discussion with the Jenkins INFRA team, we