 Thanks, everybody. Welcome to the platform special interest group meeting. Let's take a look at our agenda today. Share my screen. And here we go. Make it big enough that I can read it with my poor eyes. How's that? Okay, so just to review the agenda agenda topics first and then we'll actually run through the we'll actually do the agenda. So open action items. We had an item from last time on Natasha talking about the plug in installation manager since I don't see her yet in the meeting I assume we'll delay this when she's back to school now. Release draft or progress. Oh, like won't be able to attend so we will delay that one. So let's call it defer. And Natasha's we will also defer. I assume since she's on the east coast now again that this may be a workable time for her. Oh, like had a topic asking if we should move the configuration as code plug in work from the cloud native special interest group to the platform special interest group. If we're supposed to defer it while we wait for him to arrive then we had Alex Docker multi-arch status. You okay with that on the agenda Alex. Yes, absolutely. Great. Thank you. Then windows installer status Alex also okay on the agenda. Yes, I'm good. Okay and then a brief report on Jenkins world DevOps world for me. Markey anything that you need to get onto the agenda. Nothing for me, but they got me mostly watching this time and then I'm sure next one I will. Great. All right. No problem. Great to have you here. Super. So let's take a look at the open action items. And if I'm really smart, I can make that so we don't have a title bar. Great. So I still and I apologize. This is getting embarrassing. I have not opened the jet for the proposed rules to do Docker operating system support and platform selection rules. We have already adopted the Sentos. And my apologies for the noise in the background my hotel room air conditioner just switched on. So we have adopted Sentos as a supported platform. It's now delivered. We did it without following any particular approval process. So Oleg has an action item to open a jet for windows support policy. Same issue. Alex you're ongoing discussions with only only the evening on code signing anything you'd like to report there. Yeah, so we found out that it's basically as easy as opening a issue on the GitHub repository in the PDF. So he did that. And so we're just waiting for that to occur. We're not sure how long it'll take. But the process is fairly easy. So we'll try and document that in case needed in the future. Great. So that is that is that action is done waiting for them. Super. Okay, we had the new meeting time proposal action item and that is now done and we're meeting at the new time. I'm going to put a new action items now meeting at new time. To announce more widely so that others are aware of the change. I'd announced that in the Gitter channel but did not send it to the meeting list did not send it to the dev list or anywhere else. All right, so then we'll defer the topic for plug-in installation manager and for release drafter. Moving the Java configuration is code plug-in maintenance effort and the project to the platform. SIG feels good to me personally because I like getting more information from the meeting rather than less. They're currently in the cloud native SIG that is kind of quiet. But let's wait until Oleg is able to attend before we actually make that have that discussion in further depth. Alex, you want to give us a report on Docker multi-arch and I'm going to mute my phone so that are my source so that you don't have to hear my loud obnoxious sound. So the update on the multi-arch stuff is I believe it is complete in terms of being merged into the Jenkins for eval branch. So that is current that branch is currently building and publishing it all the images for the different architectures. The next step is going to be getting feedback on those images from various people and then merging that experimental publish into the normal published script so that it's done on trusted and in the Jenkins organization on Docker Hub. Alex, I started doing some work. I have not gotten the PRs and I'm hoping to do that next week. In changing some of the naming. So I've had a conversation with Oleg to remove some of the sort of legacy naming like the word slave. So I plan to get that work in there and I think you'll recall Oleg said a while ago how marquee may be interested in the work that you're doing. That's awesome. That's definitely needed for sure. Yeah, there's a lot of changes though that once I started peeling back that that the layers of that it I realized the actual extent of that. So it'll be definitely a large a large body of work. Yeah, I know the the windows stuff I've done for the difference. So Docker slave and Docker SSH slave and Docker JNLT slave repositories as all use the word agent so hopefully there's something there that needs to be fixed. Cool. Thank you very much for everything that you've done so far. It's helped me learn more about Docker I didn't really know anything about Docker to begin with. Great way trial by fire. All right, thanks very much. Anything else that you wanted to report on so. So, just to be sure Alex that means that arm 64 image and s and 390 x image is now being now being published under the Jenkins for eval Docker hub tree with tags there and everything. That's correct. Yes. There's also power power PC image. It's being published as well. Okay, so that's a PPC 64. Oh, do I do I remember it right. Yeah, I believe so. Okay, great. That's really good thank you. And I need to send something out on the mailing list, probably the dev mailing list, actually probably users mailing list actually about those images being available because I know they're going to send the driving force for the s 390 excellent, but it'd be good to get other people to use the other images and get some feedback as well. Excellent. Thank you. Okay. Yeah, so I'll put that as a put that into an action item for you to report in upcoming sessions. Thanks very much. Anything else on Docker multi arch. No. Okay. Next topic then Windows installer status. Alex back to you again. And the update on this is we actually have the capability now to build this on the idea that Jenkins.io. I've brought up some windows agents to allow us to do that. So, we can actually build the installer. And then, as mentioned before the code signing cert is in process. So once that's done, we should be able to have a fully automated windows installer build. Okay, so now you say CI Jenkins.io. What about trusted CI trusted also has the capability. But it'll be nice for Seattle Jenkins.io to have that capability as well. Excellent. And just for my information will continuous delivery foundation be the issuer of the certificate whose name will be on the certificate I think the old one had Kosuke's name on or the current one has Kosuke's name on it. And now be a CDF certificate or that I believe that's the case. Yes. So that the problem we've had is that his code signing cert only he can really use it. Right. So that's been difficult to automate anything so Olivier is really excited about this as well for his work on the automated release of Jenkins. Excellent. Yeah, Kosuke correctly doesn't really want to place his personal code signing certificate on a public server or on an even a trusted public server. It's it's his certificate. That makes sense. Okay. Thank you. Anything else on Windows installer status. No, I don't think so. So the last topic I had on the agenda was a report on Jenkins world and DevOps world and I think the best answer there is refer to Marquis blog post. I thought that was an excellent summary of so many things that happened at Jenkins world DevOps world. Sorry that Alex we didn't see you there but great to have a large community we had over 2000 people in San Francisco. At the conference in total really an amazing amazing effort. It was really awesome. I don't even think that blog post encompasses all of what took place there and what transpired so. Yeah, so slides slides and video recordings are I think still being processed but the commitment was that they will be made available. And there were some. Yeah, really positive results great outcomes. Those are all the topics that I had are there any other topics that we've missed. Nothing I can think of. Great, then let's call this meeting done. I will save the recording and we will. I'll post the recording later today and schedule us a next meeting in two weeks. Thanks everybody. Awesome. Have a good day everybody.