 Hello, everyone. This is Jenkins Platform Sieg meeting for August 26, 2022. Welcome, Kevin, Alissa, and everyone. Today we have a small agenda. We will talk about Open Action Items. We will talk about the preview suffix that should be removed in a few hours from the agent images. We'll talk a little bit about the requirement for Java 11, or newer, for the latest Jenkins core, and maybe say a few words about GDK17 support in Jenkins. And of course, we'll end up with DevOps World 2022, where the three of us should be there. Nice. So without further ado, let's begin with the Open Action Items. Unfortunately, it's about Mark's work and Mark isn't there today. So I don't know if he has been able to share the credential with the infrastructure team for the, I think it's an IBM S390X, something like that. We'll see maybe next time. Now, the next subject is about the preview suffix removal from the GDK17 agent images. I submitted three issues a few weeks ago about that because what I read in the community of Jenkins.io on GitHub issues and so on, was that, okay, it's officially supported GDK17. It's even part of the Jenkins core packages. So why the agents still have the suffix, you know, the preview suffix that didn't make sense to me. So I opened three issues. And then somebody called Jay Barlin took the issues and proposed three different food requests that two of them got accepted this week. So it's over, it's closed, it's merged. Thanks a lot to Jay Barlin, whoever he is or she is, I don't know. And the last one is still a work in progress. So we are looking at the PR273 for the inbound agent and maybe it will be merged later today or tomorrow. Thanks a lot for your work, Jay Barlin. That's useful to me. I will be able to change my Docker Compose file and so on. And I will not be doing one to benefit from your work. Thank you. Kevin or Lisa, anything to add for these two subjects? I don't have anything. Thank you. Next one. Required Java 11. It's been a while now that Jenkins Core Weekly needs the JDK 11. It doesn't work anymore with Java 8. We don't support it anymore. And the LTS version from September will also need the JDK 11 or the 17 one. And the major thing we saw a few weeks ago was the need to move from JT9 to JT10 because of that move to JDK 11. And in the latest release we have seen there is another thing that had to move. It is Winston that we had to move from 6.1 to 6.2. And other dependencies were upgraded which are not linked directly to the move from JDK 8 to JT11. And they were about spring security from 572 to 573 which have lots of security fixes and improvements. Regarding the next LTS baseline, so 2.361.x, maybe .3. Kevin, you know it better than I do. The proposed backports to JD10. So it's part of a later weekly release but somebody proposed a backport from JT10 from 9 to 10 into the next LTS. So that users in September will benefit from that JT10 and JDK 11 thing. Anything to add, Kevin, about that? Yeah, so we did also include some of that information in the upgrade guide. And the Basil updated the required Java 11 blog post as well. That's in the blog already. So it does mention a couple things about the JDK 11 and especially OpenJDK 11. So that is included and we do recognize that it will be coming. The fix is already kind of in place. It's just not in the release yet. But yeah, I think 2.361.3 is correct but we'll double check Mark. Thank you, Kevin. And regarding the Java 17 support engine, I haven't seen anything new. Anyone complaining about things that don't work in mode with Java 17? It's almost the contrary. Things that work kind of wonky with JDK 11 work better with Java 17. I've been running it for a few weeks now and it works beautifully for me. I haven't seen anything wrong with JDK 17. Okay, my builds are pretty small and not that ambitious but that does work for me. And that should work for a lot of other people too. Anything to add about that subject, Kevin? Not from my side. Okay, thank you. I don't know about the weekly CI Jenkins IO and the infra CI Jenkins IO. If they have been migrated to JDK 17, I can't remember. It was part of the last meeting. I don't think we talked about that. Maybe, maybe not. Mark would be able to tell us about that in the next occurrence of this meeting. Anyhow, next subject is DevOps Wall 2022 in Orlando in September. A few weeks from now, it's almost tomorrow. I'm kind of afraid. I have a workshop with Mark, Wade and John Mark-Mason about open source contributing around Jenkins. Things are beginning to take shape and I also have a talk about Android building like that. So, lots of work ahead of us. Alisa, would you have anything to share with us regarding maybe the workshop or the Jenkins contributors' summit? Anything? Yeah, so the Jenkins contributors' summits, I should be setting out an updated agenda next week. Cool. So, since the first initial conversation that you shared on Discord, Bruno, we've had a couple of new updates added to the agenda. So, I will send that communication out probably early next week with an updated agenda. And then maybe, and I'll also check in with Ayla to see how many people have signed up for the workshop, contributing to the open source workshop. So, if I can get some numbers on that, that's available. I will share that with you. Great. Thanks a lot. I don't want to tell a secret, I'm not supposed to tell, but I heard that some people wanted to be part of the contributors' summit talking about Mark how to build iOS builds with Mac instances. Am I right? Yes. Any name? That is something of interest for the platform SIG, I guess, because, yes, it's another platform. It's kind of difficult. Nothing linked to Jenkins directly, but it's kind of difficult to use Mac to build something, except if you're dealing with it on a daily basis. But it's not an easy to approach platform and putting that in the CI, wow, it's often really difficult. So, if some people want to share their experience with that and tell us how easy it is now, I'm all ears. I can't wait to hear what they have to say about that, because on a daily basis, I'm struggling with that. Anyhow. Yeah. Well, it's actually AWS that's going to be speaking about it, so it would be a very interesting topic. Yes, we can say it. So the Mac EC2 instances. Yes, thanks a lot, Alisa. I think that was our last subject on the agenda. Would anyone of us have something else to add to the agenda? A question, a remark? I don't have anything. Looks like we're good to go. That was a quick one. Thanks a lot for attending it. I think the video should be available in a few hours or at worst on Monday. If we don't see each other by then, have a wonderful weekend. Bye-bye.