 Welcome everyone to the Jenkins platform special interest group meeting. You should see the agenda on screen. Gareth, could you give me an up and down nod of your head to confirm that? Great. Thank you. All right. So welcome to the special interest group. It's for the platform reminder that we follow the Jenkins code of conduct. Proposed action proposed items, action items. Status of the master branch. I'm going to go through the agenda. I'm going to go through the agenda. I'm going to go through the pending Docker changes. And contributor summit. Any other topics you'd like to add to the agenda. I actually have one that I have just thought of. Okay. Which kind of relates to our conversation earlier. I suppose a proposal about. Adding the open container labels to all of our images. Is that, is that. I think someone had a PR for some of that. If it's the same. Yeah. I know that we're not adding them to the Jenkins images as far as I can tell, but there may well be other images or yeah, I suppose it's just making sure that consistent. Cool. Okay, good. Excellent. Any other topics to add to the agenda. All right. Let's, let's go forward then. So action item reports. Operating system. Jeff draft is still there. I would like to discuss the draft. During a track. At the contributor summit. So that'd be my proposal and that would be a place of format where we do it. Try to invite people and encourage them to. To be there. So. Any objections to that as a, as a topic for one of the tracks there. Okay. Plug-in installation manager and update center blog. So we've got the shim replacement for install plugins. Which we thought might lobby, but we don't need to even do this blog post. I think it might be good to have a blog post just talking about our idea and, and so forth. Just, you know, we don't want people to be super surprised. I don't know how many people will actually read the blog posts and still be surprised if they don't, but we can always, you know, be a little bit proactive about it. I can, I can take a jab at it. Great. Thank you. Okay. And wonderful. So. When I see. CDF Jenkins, I assume that's Kara. Kara, if I put the wrong person's name there, if it's someone else. It is me. Hi, Mark. That's great. Thanks. All right. So, so. Other changes. We've successfully completed. Our Santos image is now using adoptium. It's using adopt open JDK, just like our alpine image and our Debian image. So big win. Thanks, Alex. We have replaced Debian nine with Debian 10. We are no longer shipping. An operating system that the vendor has shifted to only doing LTS security support for it. So we are on a current operating system. Bullseye, the Debian 11 release is expected sometime in 2021, but that still gives us a year at least. Of it being Debian 10, being actively supported and maintained by the Debian community. I don't have anything additional to add to that. Jim's refinements for parallelization. Do others have anything to comment on there? No, nothing here. Okay. All right. So we had set a goal to get the CI dot Jenkins. Our master branch working and thanks to Alex. It is working and there is the proof. Excellent. Thank you, Alex. Glad to help. Gareth, you had raised the topic open container labeling. Could you give us some overview there? Help me understand what is open container. Spec. And how does that help? Yeah. So it's just about adding a consistent set of labels to all of the images that we produce. So that we can. Provide hints. The origin of those images, really. It's worth noting that you can obviously fake the labels and you don't have to add them. And there's no way of proving that the labels that you've added are in fact correct. Or validated, but it just, it helps trying to understand where something has come from. I put a pull request that's open right now in the chat. And I was wondering if that's kind of. What, what you're discussing in terms of. Yes. So that is, yeah. So there's, there seems to be two specs. So there's the label schema is one of them. And the open container. Set of labels that are another, and they're pretty much the same thing. So we could add one of those or both of those. That would be. Something like that. Yeah. And I don't remember what was holding up this PR. Label checks. Yeah, I think it's an awkward one to add because there's probably a few other labels that you want to add such as things like bill date that we don't have there. And the really useful one is to commit. Sure. That it comes from. Which you can't really add from inside the docket image. Unless you pass it in. It's either a bill dark or just pass on the command line. So I think we would need further changes to this. But I think, I think just looking at that PR, I think that's one that it's quite difficult to merge because it's going to conflict with a lot of things every time. So. Yeah. I think the other problem we had was that for windows, we fully control the build problem. And so we can add additional arguments and things like that to the build process. But for Linux, we're, we're currently using Docker hub builds. And I don't think you can inject any. Additional arguments on Docker hub builds. To do like build date and stuff like that. So that was, I think one thing that was kind of holding this up as well as. If we're still building on Docker hub, then we can't inject some of the necessary arguments. Right. So there's certain, there's sort of more of the static labels we can add because we can add them inside the Docker file, but yeah, and I think dynamic. Okay. Right. Sorry, go Mark. No, no. After you, Gary. Well, I think we're about to say the same thing. I was, is there already a proposal to switch from. I believe I have a PR open for that. Let me look. Maybe I don't. Yeah. Okay. I don't. I don't have one for the controller. I'll have to, I did. Submit one. It must be for an agent, but. I'll look. There is not a PR for the controller right now. Okay. So, so that's a, that's still a topic because. I think there is interest in. In having. And I thought that Jim Crowley had reminded noted to us that there were problems. Associated with choosing to use Docker outbase build where if we build on our own hardware. We can avoid those problems. So. I think it's, this sounds like a very reasonable interest to be reminded of and continue working. It looks like I must have closed my PR on whatever it was, because I can't find it on any of the. Docker images. So I'll see if it's closed somewhere and. All right. Anything else on open container labeling. Okay. Next one. Do a Docker. Upcoming Docker changes. So. We know we've got the install plugins. Change and Jim Crowley's multi-arch builds proposal. And then Kara. Anything you want to share with regard to the agents and how, how that non-user pull request is proceeding. No, no major updates there. Okay. I haven't, haven't heard any blockers or any. Hard stops from people who said, Hey, I, we don't want this. Have you, have you had barriers put up? That are getting in your way there that we need to be worried about. No, there may have been some work on the windows images. I need to be done possibly, but no, everything is fine there. I've just been. Pulled away from. That in the last. A week or so. Yeah, no problem. And that's, yeah, this. It'll proceed when it does. I just didn't want to have the worry that we, someone was blocking it and we needed to resolve some conflict. So thanks for doing that very much. No problem. Thank you, Mark. Okay. And we, this one, I think. The tagging tagging tagging. And announcement if we were to do open container and late, oh, and or label schema. And add more of her post tags. Those all feel like a good fit for a blog post saying, Hey, here's what we're doing and why we're doing it. Anything else on pending Docker image changes. Last topic on my list was the contributor summit. And I've got. A note on the contributor summit here. That what I've done is I've drafted up a section proposing a Jenkins on Docker track, or we could call it. Just a. A. Jenkins platform sing track Jenkins platforms track. The contributor summit will be February 23, 24 and 25. The first session will be inviting everyone to come together. 90 minutes of that session will be. Talking and presenting what we've done so far and what we're envisioning next from people who are leads of various special interest groups or officers in various roles. Then the last 30 minutes we'll use to coordinate how we're going to use the next 48 hours. The contributor summit will be February 23, 24 and 25. And then we'll do a concluding session on how we're going to use the next 48 hours. In that sequence to do these tracks and find times that work for people. Then after that 48 hour period. The, when these tracks have all met. Talk, then we'll do a concluding session. And here from the various track leaders to talk about, Hey, we, we found this, we found this. The idea is we'll make things fit with our various time zones during that 48 hour period. I'll send out registration information on the plat on the, the contributor summit. It'll be a Google form based on conversations in Jenkins governance of a day or two ago. Any questions or concerns on the concept of contributor summit or the platform six involvement. Is it wider than just Jenkins on Docker and it also includes Jenkins on Kubernetes. Ah, good, good point. So maybe what we should call it is Jenkins on containers. Yeah, because, because my thought was this, I just wanted a platform track, but maybe Jenkins on containers is a much better choice for a name because Docker is not the only container spec in the world, is it? Although my assumption is we would not talk here about running Jenkins inside a free BSD jail, much as I love my jails and much as I think they're so cool. That's not the topic here. Come on, you might get a Tyler to come to that as free BSD involved. Exactly. And I might get Jim Clemaw to come as well, but, but that's, I have to admit, much as I love jails, it's not, it's not a common thing. Okay. Anything else on, on contributor summit. Okay, so let's go to that covered all the topics that I've seen for today's meeting. Any other topics we need to discuss? I guess one open question is, should we meet as a platform, see the, the day after the contributor summit ends and my preference is probably not, let's cancel the next meeting in favor of, in favor of attending the contributor summit. Do you know what the time zone of the content contribute to summit is going to be? Yeah, so the opening session will be from, I think it's scheduled from 15 to 1700 hours UTC. So it'll be European, European time zone for those because those seem to work well for us for large group meetings, then we'll do this, we'll find times that the other tracks work based on who's involved in the track. So we'll go through that three through 25. First session. 23 at, and I think it was, I think it's 1500 UTC. Alex I apologize on that it's a little early, but hopefully you'll be able to join us for at least one of those sessions. I have a work conflict. That's right. It's not available at all that time. Yeah, that's, so all right. Any objections to the proposal to cancel the next meeting in preference for the contributor summit. I think that makes sense to me. All right. So next meeting will be next meeting is in four weeks then. Thanks everybody. Look for the, look for the invitation of the contributor summit coming to your email soon. Thank you. Thanks.