[Jenkins-infra] Moving ci.jenkins.io to Java 11

[Olblak]

The first thing would be to open an jira ticket with the requirements and the expected results. 
Then "someone" need to open a PR on jenkins-infra/jenkins-infra <https://github.com/jenkins-infra/jenkins-infra> with the approriated puppet code in order to use java11 on ci.jenkins.io without affecting trusted.ci neither cert-ci. 

While it's not totally related, I am still trying to find so time to work on INFRA-2005 <https://issues.jenkins-ci.org/browse/INFRA-2005> to have different installed plugin and init groovy script per instances.

> Correction, it might not be *that* simple actually, given we must make sure agents are also bumped to JDK11 at the same time.
It seems to me that we must:
* Update jenkins master docker image to 'jenkins/jenkins:lts-jdk11'
* Update vm init script to install java11.
* Let die existing vm agents, or kill all of them from azure portal

> The instance is running latest of all plugins I suppose?
Daniel regularly updates plugins

---
-> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---




On Tue, Apr 16, 2019, at 11:39 PM, Baptiste Mathus wrote:
> Correction, it might not be *that* simple actually, given we must make sure agents are also bumped to JDK11 at the same time.
> 
> I still think we should look into it, but this needs some testing and assessment of the current setup IMO.
> 
> Le mar. 16 avr. 2019 à 20:57, Baptiste Mathus <ml at batmat.net> a écrit :
>> Answers inline.
>> 
>> Le mar. 16 avr. 2019 à 17:33, Vernin Olivier <olivier at vernin.me> a écrit :
>>> __
>>> Is there anything else to do than creating a backup of the jenkins home and then update the docker image to use jenkins/jenkins:lts-jdk11?
>> 
>> Nope indeed, it should be very simple. Doing what you're saying sounds perfect. 
>> The instance is running latest of all plugins I suppose?
>> 
>>> 
>>> 
>>> Baptiste did you receive your support bundle?
>> 
>> No. If someone sent it, I have missed it somehow. Was it sent?
>> 
>> Thanks!
>> 
>>> 
>>> 
>>> Olivier
>>> 
>>> ---
>>> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
>>> ---
>>> 
>>> 
>>> On Tue, Apr 16, 2019, at 2:10 PM, Baptiste Mathus wrote:
>>>> Anyone with enough permissions to provide this of the band? Thanks
>>>> 
>>>> Le mer. 3 avr. 2019 à 21:14, Baptiste Mathus <ml at batmat.net> a écrit :
>>>>> Cool. We are going to look into this. Not sure on which timeline yet exactly, but I do think it would be a very valuable situation to be in.
>>>>> Be able to tell users out there that we were confident enough to switch main instance of the Jenkins Project is a clear signal.
>>>>> 
>>>>> Would it be maybe possible to receive a support bundle off the band, so we can look at possible specifics, like the list and versions of plugins installed, etc.?
>>>>> 
>>>>> https://ci.jenkins.io/support/
>>>>> 
>>>>> Thanks!
>>>>> 
>>>>> Le mer. 3 avr. 2019 à 18:06, R. Tyler Croy <rtyler at brokenco.de> a écrit :
>>>>>> (replies inline)
>>>>>> 
>>>>>> On Wed, 03 Apr 2019, Adrien Lecharpentier wrote:
>>>>>> 
>>>>>> > Well, 2.164 and 2.164.1 are the first releases of Jenkins to officially support
>>>>>> > JDK11.
>>>>>> > We already are running 2.164.1 so it's "just" a matter of upgrading the JVM we
>>>>>> > run the instance with.
>>>>>> 
>>>>>> Aha! I misunderstood the timeline for JDK11, I thought it was in the weeklies
>>>>>> only still.
>>>>>> 
>>>>>> 
>>>>>> Well if that's the case, which one of you folks are going to plan the migration
>>>>>> ;)
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> GitHub: https://github.com/rtyler
>>>>>> 
>>>>>> GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2
>>>>>> _______________________________________________
>>>>>> Jenkins-infra mailing list
>>>>>> Jenkins-infra at lists.jenkins-ci.org
>>>>>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>>>> _______________________________________________
>>>> Jenkins-infra mailing list
>>>> Jenkins-infra at lists.jenkins-ci.org
>>>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>>>> 
>>> 
>>> _______________________________________________
>>>  Jenkins-infra mailing list
>>> Jenkins-infra at lists.jenkins-ci.org
>>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20190417/4ec5afbd/attachment-0001.html>