<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>The first thing would be to open an jira ticket with the requirements and the expected results. <br></div><div>Then "someone" need to open a PR on <a href="https://github.com/jenkins-infra/jenkins-infra">jenkins-infra/jenkins-infra</a> with the approriated puppet code in order to use java11 on ci.jenkins.io without affecting trusted.ci neither cert-ci. <br></div><div><br></div><div>While it's not totally related, I am still trying to find so time to work on <a href="https://issues.jenkins-ci.org/browse/INFRA-2005">INFRA-2005</a> to have different installed plugin and init groovy script per instances.<br></div><div><br></div><blockquote type="cite"><div>Correction, it might not be *that* simple actually, given we must make sure agents are also bumped to JDK11 at the same time.<br></div></blockquote><div>It seems to me that we must:<br></div><div>* Update jenkins master docker image to 'jenkins/jenkins:lts-jdk11'<br></div><div>* Update vm init script to install java11.<br></div><div>* Let die existing vm agents, or kill all of them from azure portal<br></div><div><br></div><blockquote type="cite"><div>The instance is running latest of all plugins I suppose?<br></div></blockquote><div>Daniel regularly updates plugins<br></div><div> <br></div><div id="sig64200129"><div class="signature">---</div><div class="signature">-> gpg --keyserver keys.gnupg.net --recv-key 52210D3D</div><div class="signature">---</div><div class="signature"><br></div><div class="signature"><br></div></div><div><br></div><div><br></div><div>On Tue, Apr 16, 2019, at 11:39 PM, Baptiste Mathus wrote:<br></div><blockquote type="cite" id="qt"><div dir="ltr"><div>Correction, it might not be *that* simple actually, given we must make sure agents are also bumped to JDK11 at the same time.<br></div><div><br></div><div>I still think we should look into it, but this needs some testing and assessment of the current setup IMO.<br></div></div><div><br></div><div class="qt-gmail_quote"><div class="qt-gmail_attr" dir="ltr">Le mar. 16 avr. 2019 à 20:57, Baptiste Mathus <<a href="mailto:ml@batmat.net">ml@batmat.net</a>> a écrit :<br></div><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-color:rgb(204, 204, 204);border-left-style:solid;border-left-width:1px;padding-left:1ex;" class="qt-gmail_quote"><div dir="auto"><div><div>Answers inline.<br></div><div><br></div><div class="qt-gmail_quote"><div class="qt-gmail_attr" dir="ltr">Le mar. 16 avr. 2019 à 17:33, Vernin Olivier <<a href="mailto:olivier@vernin.me">olivier@vernin.me</a>> a écrit :<br></div><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-color:rgb(204, 204, 204);border-left-style:solid;border-left-width:1px;padding-left:1ex;" class="qt-gmail_quote"><div><u></u><br></div><div><div>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?<br></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Nope indeed, it should be very simple. Doing what you're saying sounds perfect. <br></div><div dir="auto">The instance is running latest of all plugins I suppose?<br></div><div dir="auto"><br></div><div dir="auto"><div class="qt-gmail_quote"><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-color:rgb(204, 204, 204);border-left-style:solid;border-left-width:1px;padding-left:1ex;" class="qt-gmail_quote"><div><div><br></div><div><br></div><div>Baptiste did you receive your support bundle?<br></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">No. If someone sent it, I have missed it somehow. Was it sent?<br></div><div dir="auto"><br></div><div dir="auto">Thanks!<br></div><div dir="auto"><br></div><div dir="auto"><div class="qt-gmail_quote"><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-color:rgb(204, 204, 204);border-left-style:solid;border-left-width:1px;padding-left:1ex;" class="qt-gmail_quote"><div><div><br></div><div><br></div><div id="qt-gmail-m_-8729969131109436601m_-8963902271472111979sig64199697"><div class="qt-gmail-m_-8729969131109436601m_-8963902271472111979signature">Olivier<br></div><div class="qt-gmail-m_-8729969131109436601m_-8963902271472111979signature"><br></div><div class="qt-gmail-m_-8729969131109436601m_-8963902271472111979signature">---<br></div><div class="qt-gmail-m_-8729969131109436601m_-8963902271472111979signature">gpg --keyserver <a rel="noreferrer" href="http://keys.gnupg.net">keys.gnupg.net</a> --recv-key 52210D3D<br></div><div class="qt-gmail-m_-8729969131109436601m_-8963902271472111979signature">---<br></div></div><div><br></div><div><br></div><div>On Tue, Apr 16, 2019, at 2:10 PM, Baptiste Mathus wrote:<br></div><blockquote id="qt-gmail-m_-8729969131109436601m_-8963902271472111979qt" type="cite"><div dir="auto">Anyone with enough permissions to provide this of the band? Thanks<br></div><div><br></div><div class="qt-gmail-m_-8729969131109436601m_-8963902271472111979qt-gmail_quote"><div dir="ltr" class="qt-gmail-m_-8729969131109436601m_-8963902271472111979qt-gmail_attr">Le mer. 3 avr. 2019 à 21:14, Baptiste Mathus <<a rel="noreferrer" href="mailto:ml@batmat.net">ml@batmat.net</a>> a écrit :<br></div><blockquote class="qt-gmail-m_-8729969131109436601m_-8963902271472111979qt-gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-color:rgb(204, 204, 204);border-left-style:solid;border-left-width:1px;padding-left:1ex;"><div dir="ltr"><div dir="ltr"><div>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.<br></div><div><div><div>Be able to tell users out there that we were confident enough to switch main instance of the Jenkins Project is a clear signal.<br></div><div><br></div><div>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.?<br></div></div></div><div><br></div><div><a href="https://ci.jenkins.io/support/" rel="noreferrer noreferrer">https://ci.jenkins.io/support/</a><br></div><div><br></div><div>Thanks!<br></div></div></div><div><br></div><div class="qt-gmail-m_-8729969131109436601m_-8963902271472111979qt-gmail_quote"><div dir="ltr" class="qt-gmail-m_-8729969131109436601m_-8963902271472111979qt-gmail_attr">Le mer. 3 avr. 2019 à 18:06, R. Tyler Croy <<a href="mailto:rtyler@brokenco.de" rel="noreferrer noreferrer">rtyler@brokenco.de</a>> a écrit :<br></div><blockquote class="qt-gmail-m_-8729969131109436601m_-8963902271472111979qt-gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-color:rgb(204, 204, 204);border-left-style:solid;border-left-width:1px;padding-left:1ex;"><div>(replies inline)<br></div><div><br></div><div>On Wed, 03 Apr 2019, Adrien Lecharpentier wrote:<br></div><div><br></div><div>> Well, 2.164 and 2.164.1 are the first releases of Jenkins to officially support<br></div><div>> JDK11.<br></div><div>> We already are running 2.164.1 so it's "just" a matter of upgrading the JVM we<br></div><div>> run the instance with.<br></div><div><br></div><div>Aha! I misunderstood the timeline for JDK11, I thought it was in the weeklies<br></div><div>only still.<br></div><div><br></div><div><br></div><div>Well if that's the case, which one of you folks are going to plan the migration<br></div><div>;)<br></div><div><br></div><div><br></div><div>--<br></div><div>GitHub: <a href="https://github.com/rtyler" rel="noreferrer noreferrer noreferrer">https://github.com/rtyler</a><br></div><div><br></div><div>GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2<br></div><div>_______________________________________________<br></div><div>Jenkins-infra mailing list<br></div><div><a href="mailto:Jenkins-infra@lists.jenkins-ci.org" rel="noreferrer noreferrer">Jenkins-infra@lists.jenkins-ci.org</a><br></div><div><a href="http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra" rel="noreferrer noreferrer noreferrer">http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra</a><br></div></blockquote></div></blockquote></div><div>_______________________________________________<br></div><div>Jenkins-infra mailing list<br></div><div><a rel="noreferrer" href="mailto:Jenkins-infra@lists.jenkins-ci.org">Jenkins-infra@lists.jenkins-ci.org</a><br></div><div><a rel="noreferrer" href="http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra">http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra</a><br></div><div><br></div></blockquote><div><br></div></div><div>_______________________________________________<br></div><div> Jenkins-infra mailing list<br></div><div> <a rel="noreferrer" href="mailto:Jenkins-infra@lists.jenkins-ci.org">Jenkins-infra@lists.jenkins-ci.org</a><br></div><div> <a rel="noreferrer noreferrer" href="http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra">http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra</a><br></div></blockquote></div></div></div></blockquote></div></blockquote><div><br></div></body></html>