 And I'm going to start immediately sharing my screen. Welcome to the Jenkins platform special interest group. It is the 10th of September. A reminder that we follow the Jenkins code of conduct. So thanks very much for being here. Let's review the action, the agenda items action items. Then we'll talk about adopt open JDK eight for Docker on Debian. Retirement schedule for Debian nine and our doctor images. Removing install plugins.sh. I'll give a brief status on our PC 64 and status on conversations with Oracle cloud. So Alex, anything else? No, I think that's a good list. Okay, so let's go over the action items. I still have to do that Jeff. It will be at least another week before I work on it with Olivier unavailable infrastructures kept me hopping busy. We've got the Docker build rework PR Alex anything you've been much closer to that than I have I apologize that I haven't been as involved as I should. What anything you want to report there. So it's actually it's been merged now. So that action items. Oh, excellent. Okay. There are some follow on tasks that we the PR itself has been merged. Excellent. Thank you. And has it has it shown the desired positive effect on Docker build time on any of those things is, I haven't heard any outraged complaints or crying about the change that that surprises me and impresses me says that it must be in that positive. Well, it actually needs one change to the Jenkins file for it to actually be working fully. So I need to make up that's one of the tasks that needs to be done. I need to go ahead and update the Jenkins file. So, I'll be working on that pull request for that. Thank you. Okay. So I have a couple of options for adopt open JDK. So anything to report there Alex. Yeah, so I found they have a page adopt open JDK does has a page with all the different install options. So I'll look at some PRs for adding that to the centos or other images because No, it's only sent to us that we need to do that. So yeah, I'll do that on some to us and do some local testing. Yeah, that one that one I'm still, I'm still sort of wrestling using adopt open JDK has the benefit that then we would be using only one JDK. The centos people are usually very closely coupled to red hat who has their own JDK distribution that they're quite serious about. Okay, good. Thank you. And then install plugins.sh. I'm working on that PR right now. It's a pretty simple car. I should have a submit it today. So tell us tell us more about what will that mean there will be a message when install plugins.sh is run or correct. So we've done that with plugins. Which was an older method for installing plugins. And actually as part of my PR I'm just going to delete that the old plugins.sh because it's been deprecated for some time now. So I'm kind of moving the warning that was in that about deprecation over to install plugin.sh and updating the message to point to the new method. And I think I saw that plugin manager is being called now in the build process. Is that the plugin installation manager is already being called? It can be option. Okay. There's a wrapper script that the jar file is included now in the image. And the there's a shell script that wraps the jar file so you don't have to do the Java, dash jar, invocation. And that was Tim Jacob that added that. Excellent. Okay. Oh, and I still have a blog post to do to associate with that. That's and I've been talking with the update center changes have been. Let's see update center mirrors and plugin installation manager. We've had really some significant improvements recently with update centers are now or, or I should say differently, the mirrors are now using HTTPS instead of HTTP. The update center is has gained a bunch of new new intelligence thanks to Daniel Vex work, and then plugin installation manager so good infrastructure blog post. So still to do. I didn't mean to interrupt you on install plugins that I say anything else you wanted to note there. No, no, that's all good. Okay, great. All right. So we have a new update for Docker on deviant. We do have a PR in place for buster. We need to determine if we want to do that for stretch. Buster is the newer is 10 right and stretches nine. Correct. I propose that we decide right now, intentionally not doing PR for stretch stretch and of life. I saw a posting actually stretch official end of life has already happened in that they've switched to LTS support mode. And so, so it was back in July when it ended the normal support mode and went into LTS mode. And so, but the LTS mode still means we get security fixes so we're okay. But I think, once they release bullseye in sometime in 2021 stretch is should be off our list. Okay, which brings us to our next topic retirement schedule for Debbie and nine in our Docker images now to educate me on this one. Alex, how, how do we what's an effective way to announce the retirement of an image so we advise people to switch to the buster image that I'm not sure I don't know if there's a good idea to just add something to the repository on Docker hub, or, or what I don't know what other projects do. So maybe we need to do some research determine best practices. Okay, good idea. Yes, to see how other projects notify their consumers of obsolescence. So as I think about it, the, the open JDK people for instance, don't notify at all they stop supporting alpine and I got no no indication of the stop it just didn't, didn't iterate any longer. So, that's one possibility is just stop. Yeah, I suspect that's not, not the popular possibility so we won't we, we won't get a lot of love for our from our consumers from our users. Okay. All right, how about let's give me the action item to propose a retirement plan, including a communication plan, because that fits nicely with the fits with the Jeff responsibility. I started on that Jeff sooner, just right by saying hey we need to do this retiring devian nine, because the operating system itself will retire. Okay. So anything else on devian nine devian that's no I don't think so. And install dash plugins.sh I think we discussed in the action item anything else there. PowerPC le 64 le agent access. So about a week ago. During things where I was busy with other stuff. The lost that I lost access to the power PC agent I'd been using that IBM had donated. I was in the middle of something it didn't have time to even ask for their help to get it restarted I sent that request last night and Rafael responded to me, dark of a night for him in Brazil, he responded that he would look at it today. It's been available, unavailable for a longer time on Seattle Jenkins that I owe because I couldn't figure out get to connect. Once they provided again, I'll reconnect it to my test cluster and to see it Jenkins that I owe and we'll watch to see how it behaves. Okay. Then we've also started conversations with Oracle cloud. And so I was involved in a conversation with Corey Quinn, and that conversation was around Oracle cloud and how Oracle cloud is evolving and Oracle contacted us, and as a said hey they would like to be involved more with the Jenkins project. And so we were discussing with them possible things including communication so hardware slash compute resource and bandwidth for mirroring. Nice. Yeah, it's, and it's as a matter of course we have to be sure that we're ready to use compute capacity that's available to us and may have to switch from one cloud to another, depending on who's willing to donate. So this is makes for an interesting discussion of conversations will continue, and I'll keep sharing status. Dude, is there a good age that goes over there, what they support. Like, do they have something similar to like AC, or ACI for instance, or things like that, you know, yes, and good, good point. Yes, they have a managed Kubernetes offering. Yes, they are just bringing online now a solution like ACI. So they don't, I think, I like the way Tyler was discussing with them initially he noted. Hey, when Microsoft brought their ACI solution online we were one of the early adopters, and we help them understand and refine their offering. Oracle is in sort of an early adopter phase right now with their, their container instance style solution. Gotcha. And they also, they have a different one of the interesting angles is they have a different focus from their history. Right. And I liked how they described it they note that Google and Amazon both had to do massive compute projects for their business needs, and they did these scale wide business need challenges and then they began selling those to the market. Oracle needs to be able to sell, you know, database kind of products and enterprise things. And so they started from an enterprise style view. And so it gives them a different, different approach. And because they're a relatively newer entry, they have a lower price point as well. So now we, we aren't, I don't think the Jenkins project is interested in paying cash to Oracle. That's, that's not really for me on the table at all because cloud continuous delivery foundation funds are our budget to Azure. And we need to get be sure we get volunteers and donors. Right. All right. That covered all the topics we had for agenda anything else for today. Nothing for me. All right. Well, Alex, thanks very much. An archive of the recording will be posted. And on we go with the actions. Thanks very much. All right, thank you.