Belated +1 for a standalone plugin here. On my instances I would like to disable Oracle JDK installer and eventually remove it, so I am totally in favor of having a separate plugin.
I also created tickets to make the scope of the jdk-tool plugin more clear: - https://issues.jenkins-ci.org/browse/JENKINS-57394 - https://issues.jenkins-ci.org/browse/JENKINS-57395 The new plugin in https://github.com/jenkinsci/adoptopenjdk-plugin also does not rely on the Jenkins update center polling, and this is a good thing IMHO. On the other hand, I am not sure about https://github.com/jenkinsci/adoptopenjdk-plugin/blob/master/src/main/resources/io/jenkins/plugins/adoptopenjdk/AdoptOpenJDKInstaller/config.jelly#L35-L46 . It may lead to a really long list in the future BR, Oleg On Monday, May 6, 2019 at 8:09:04 PM UTC+2, Mads Mohr Christensen wrote: > > > > On 6 May 2019, at 16.06, Baptiste Mathus <[email protected] <javascript:>> > wrote: > > * download things from outside once, > * *and* make it dead-simple to upload it to your binary internal server > (artifactory, Nexus...), > * and then download tools from there (your internal binary server). > > > The jdk-tool plugin downloads the binary from Oracle and uses a cache on > the master for uploading to other nodes. > I thought about adding this to my new plugin but chose to keep it simple. > > It shouldn’t be too hard to add this later. > > /M > -- 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/7c80ba63-275f-4eef-8888-441fa8531a9c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
