 Welcome to the platform special interest group the 5th of November 2020. Let's take a look at the agenda. And work to there. So topics open action items. Adopt open JDK for Docker on Debian retirement plan for Debbie and stretch nine in our Docker images. Status report on power PC 64 agent access status report on work on Windows server LTSC 2019 Docker images. Status report on Oracle cloud by me as your credit offer status report is another platform topic and proposing a new meeting time anything else that you'd like to propose. Okay, let's go ahead. So, I still have the action to open the Jenkins enhancement proposal for Docker operating system support. I've run through a script that looks for inconsistencies and outdated dependencies in our images, and this that includes the Jenkins controller, the various forms of agents including SSH agent and Docker inbound agent. And I was impressed at how relatively few astonishing inconsistencies I found I was expecting to find many many because they're relatively independently maintained. One of the things that I did see is we're still using JDK 80242 242 on the image that is probably the most used image, and that JDK is now quite out of date, it should be 272. And I think that means that it's probably open JDK, not adopt open JDK. And so that's a change but that change will naturally come as we switch to from Debbie and nine to deviant 10 for the LTS image because the deviant 10 based image is already using JDK 80242. So that one inconsistency I found will resolve itself as we make the transition away from Debbie and nine. Any question on the that topic. So Alex's action items will leave open. I did want to share that the install plugins.sh script. The work with dependencies and has to have every single plugin listed is now now has a much better replacement included in the Docker image, and our install guide actually uses the new version. So this right here, this run line here installs all the plugins needed to run Jenkins Blue Ocean with a single command line and one single argument. It makes it look so much better and the tutorial and the install guide feels better because of it. So thanks to to Tim Jacome for integrating that and Alex for getting it included in the Docker image. The tutorials also do the same thing they use that nice simple one line command to install the entire blue ocean. The next topic was a blog post on plugin installation manager and update center. Sorry, I haven't done you have done that yet. That's let me just put that as a to do for me. It'll stay as an action. I hope to get to that before our next meeting. It won't be this week, but I hope before this before we meet again in two weeks. And then Jim Crowley had the action item for refinements on parallelization and multi art support. And that is in progress based on conversations in the header chat. Thanks to Jim for his work there. We're literally in the morning now his time in the US where he's based in upstate New York. Next topic adopt open JDK for Docker on Debian. I believe has been merged. So, since it's been merged, I think we're good to go. So let's just note that as done needs test and confirmation. Next topic was. Let me just mention that Gareth in terms of adopt. Retirement plan for Debian stretch nine in our Docker images. So what this, this really means is that we've got Debian nine that is the base of our Docker images for the LPS image. And Debian nine in early 2021 will be unsupported. So we're going to start a Debian nine. Then means that we need to get off Debian nine. So my proposal would be that we announced that we will switch the LTS tag from using using Debian nine to using Debian 10. As of December when we released two dot 263.1 is the LTS. We're supposed to send a send that proposal to the Jenkins dev developers list and prepare a blog post. I don't know that I don't think that most users will see that as a as a significant change. Our slim image is already using Debian 10. And doesn't show an awful lot of changes and even if there are changes our users will need to adapt Debian nine is going off support. All right, next topic was power PC 64 le agent access proud, proud and grateful that Alex and Raphael of IBM were a Alex from Broadcom and Raphael of IBM were able to get our connection to the power PC 64 le agent restored So you can now use the PC 64 le on your CI dot Jenkins IO jobs. We had several jobs that have used it in the past and we'll continue broadening those nice fast machine. Great way to check platform portability. You want to report on Windows Server 2019 progress. Certainly. Actually, I've just lost power again. So if I disappear, that's, that's why. So we have made pretty good progress with the 2019 LTSC hosts that are being built for AWS and Azure and they seem to be running successfully. There's probably the property probably have got some places where we haven't updated those yet. So I'll do a pass of those to make sure that they're running in all environments later on. The adopt open JDK repository has been forked. So that we can add 2019 LTSC images under the Jenkins for eval organization for a period of time until the pull request can be merged and they can be officially supported by adopt open JDK Those images appear to be building correctly and are being published into the Jenkins for eval Docker hub repo. I've got a few I've still have a few issues with some of the tags that I'm hoping to resolve today. And then there is a catch up. And then there's a PR to add the 2019 LTSC based builds for the Jenkins Docker images. As soon as I've got the tags sorted. That's excellent. Okay, so, so the Jenkins for eval base image. I still think that is ingenious. So the, the pull request to adopt open JDK in hopes that they will eventually provide us a standard image. Windows based that then automatically upgrades to new versions of JDK every time they release a new version is really attractive and in the interim you're using that image definition as the base image. That's great. Yeah, we'll have to see how that goes with the updates that they publish. There may be another job that we need to run to keep that in sync. And is this a place where I haven't looked at depend about as a way to manage these updates. I know we have a 242 in one location. Is there is that is that something that depend about can help us manage or not really possibly say I actually think if the community kind of want to build images on another version of windows to say they want to lock to 2004 or something like that, or maybe even 20 h2. Then it should be possible to use depend about to stay to keep it up to date. From the, the actual official Jenkins releases. That's not something we've tried, but I think we can do that with you can do that with a multi stage build dependable will update images in that way. So, yeah, I think I think that is an option. There's something we should document and blog about, I think, because it's it's I'm sure there's going to be someone asking on how to do that so was it may not be something that we, we want to officially support. We should be able to provide guidance on how to do it. Okay, okay, so that would allow someone who says who I must have 20 h2 to say today. Okay, if you must have 20 h2 you'll need to build your own image and here's how you do it. And if you use this dependable technique. It will keep you up to date as a result. Yeah. Excellent. Anything else, Gareth. Yes, I think that's everything on there. I'll, I'll, I'll provide a link to the Jenkins Docker image PR, but I'll do that. I haven't actually created the PR yet so have it locally. Great. Excellent. Thank you. It's exceptional. Thank you. Thank you. All right. Next topic then Oracle cloud. Oracle has asked us to express their interest in helping the Jenkins project and getting more involved. Unfortunately, I've dropped the ball on this one been busy on other things. One of their of the Oracle team asked just yesterday for a second time hey Mark, how's your experiment going with Oracle container instances, and I haven't started that so Mark, I should start the experiment probably this weekend and share the results with Oracle and with others. Yet no if I'll blog about it, it'll depend on the results if they're positive. I'll likely blog about it just because hey the experience is worthwhile to share. Next topic, Azure credit offer. So, what the background on this is that we currently pay about $10,000 a month to Microsoft for the Azure services and hardware that we use. And our Microsoft customer success manager asked us hey would you like to apply for this credit offer that gives credit to where they causes. And so we submitted our application, and we hope that they will give some offsetting donation to reduce the costs that are currently played paid by the continuous delivery foundation for our Azure infrastructure. We've provided some will provide some additional detail to them hope that that application process goes through and hope to hear within the next two to four weeks, whether or not we were accepted. Last topic, proposing a new meeting time meeting participation has gone down and right now this this particular meeting is starts at 5am my local time here in in northern Colorado and that's awfully early. I propose that I'll send out a survey to ask the typical participants, what time they would like to meet instead in hopes of getting more participation in this session so that we can give each other status reports. This time doesn't work for me personally, and I would like to avoid being up at 430 in the morning just so that I can start a meeting this early. But if anything else that I should be that we should be discussing today. No, I don't think so. All right, let's call this meeting done then thanks very much. And see you.