 Welcome everyone, this is the Jenkins Platform Sieg meeting, we are at the end of February 27th of February, yes, 2024. Today around the table, we have Kevin Martens and myself. Hello, Kevin. We don't have that many things on the agenda today. The Bolly played things, I would say like every two weeks, the open action items, the Java 21, the work that got released on agent and controller images, the work in progress on images, the Docker base quick start tutorials. And I thought we would have Nick Riemann today talking about the plugin installation tool, but he's not there. So I don't know about the progress he may have made on this subject. So let's get started. The Blue Ocean Docker container, I know we have to communicate its deprecation in a way or another. I got another question, not I. The Jenkins community got a question today about how to update the Blue Ocean Docker container on community.genkin.io. So some people still use it and want to update it and know that is not possible. This thing is deprecated. So it's not a good idea to still use it and try to tweak it to get it to work with the latest Jenkins controller version. The best thing you should do is start from a fresh Jenkins controller Docker image and then add the Blue Ocean plugin if you really need it. And frankly, these days we had a discussion during the latest Jenkins contributor summit in Brussels, Belgium at the beginning of February about getting rid of Blue Ocean for the infrastructure and users of Jenkins. There is another plugin called Pipeline GrabView if I'm not mistaken. And frankly, for most of the uses of Blue Ocean, it does the job. We are in the process of rewriting the Docker container tutorials. We'll talk about that in a few minutes. And most of them are based on Blue Ocean. And frankly, it's pretty easy to rewrite those tutorials, getting rid of Blue Ocean and switching to the Pipeline GrabView. So yeah, if you want to do that, please give a chance to Pipeline GrabView instead of trying to use the Blue Ocean Docker container which is outdated. Okay, done with the rant. Now, we've had the Java 21 support two plus two plus two Java support plan mark. Mark is not available today. So I haven't seen any new things in the discussion regarding the Jenkins enhancement proposal by Mark, you know, February, after first them is more or less called. So I don't think there is anything new. As far as I know, ooh, okay. Yes, last comment was on January. So once again, during the latest contributor summit, there were some very interesting discussions about how to handle a date of the Java version supported by Jenkins. So of course, we will still discuss it with the rest of the community and make a final proposal one of these days. Kevin, would you have any question or comment about that? Yeah, no additional contacts on my side. Thank you. Thank you, Kevin. Now, for the release work on agent and contributor images, nothing really fancy these days. We have of course two new contributor weekly 2.446 at 2.447. Of course, we had the update to the Jenkins of the right version. And frankly, the only thing that I noticed was that we moved from an older version of Bookworm Linux to 24 February 11th version. And that's all. Of course, we had a new LTS controller LTS 2.440.1 image with of course, quite a few changes because it's 12 weeks also of changes from an LTS to another LTS. So we had quite a lot of bumps in the version of the supported operating system for UB9, DBN, Alpine Linux. We have changed the latest Java releases because we were using some, I would say a few weeks or a few months old Java releases. And there is a process of releasing regularly Java releases. So we had to use the latest Java releases. We also have moved, I think it's most of Mark's work, consistent jailing arcs within Java version because in several Docker files, we had different ways of putting argument into jailing command. In fact, not all images are built this way, but for some of our Docker images, we start with downloading the JDK from Tamarin and then we run the jailing command with some arguments in order to have a very tailored version of the JDK for the architecture and the operating system we are building on. We also have had the Java 21 Windows container and Mark and Kenneth Salerno have worked on removing the PPC64LE JDK 21 preview images and repair them with an official JDK 21 image. Yeah, and that's most of the thing that I noted in the latest LTS. For the Docker agent, there is nothing new happening and for the SSH agent, we only had one version bump leading to just one new release, which also was about a date of the Debian Bookworm Linux to the February version. We still have the same work in progress on images for the controller. So it's mostly Hervé's work about adapting the JDK 11 and JDK 17 manifests for Windows. It has been running for a while. It's still in draft, it has not been reviewed yet. And now for the last subject I had in mind, it's about Docker-based quick start tutorials. So we've been working on that since last year, I would say we created a subject, we proposed a subject for GSOC 2023 about how to rewrite the existing Docker tutorials that were pretty intimidating, I would say before even touching anything directly linked to Jenkins, you had to do quite a lot of configuration. Frankly, as a new user, I don't know if I would have made it to the end of the tutorial anyhow. So we were working last year with a contributor of GSOC 2023, Ashutak Saxena and he went with an idea of a new repository in which you would have Docker files and a Docker compost file defined and using just one command would allow you to have a Jenkins instance working on your machine in the cloud, wherever, we just one command. That was the goal of that. And so after GSOC project finished, we decided to change the documentation in order to use that repository. And we already have done the Maven tutorial, the Python tutorial, the Node tutorial has been written, but it's currently in the review. Thank you, Kevin, for the review, by the way. And now we're working on the multi-branch pipeline tutorial. The last one we will have to work on in the main Docker installation tutorial is not the Docker installation, it's a Jenkins installation thanks to Docker. And I think in this one, we also have the infamous Docker in Docker and that may not be needed. So that's why we are rewriting that. After that, we should be more or less done with the rewriting of the tutorials using Docker. Kevin, would you have any comment or question about the subject? Just thank you for all the work on this, Bruno, and thanks for getting everything to this point. I know the Google Summer code stuff ended a while ago, but the work that you and Ashutosh have done is great. And just really look forward to when we get to that installation documentation piece, because I'm ready to help. Yeah, and it's already helping people. That's what I like. In fact, sometimes in GitHub or in community.genkins.io, I have some people saying, oh, I've tried the Docker tutorial. It doesn't work for me. It's too hard or whatever you say. Hey, could you just try that? And sometimes it works. And people give us some feedback, say, oh, it worked for me. So yeah, for me, that's a gift, you know, working or something and having people use it and it simplifies their daily routine with Jenkins. Wow, that's something amazing. So yeah, we'll continue doing that. Yeah, Kevin, would you have any other subject I forgot to address today? The only thing that I had, that I thought could potentially be interesting here is doing the changelog for the weekly release today. It looks like there was an update to Stapler. And I don't know if that's necessarily relevant here or if that would just be better kept for other meetings. But yeah, I figured I'd throw it out there since it was specifically a developer note. Okay, would you have a link to share or something for me? Or I will find it, but, oh, thank you. Yeah, sorry, I was just looking for the link. Yeah, that's okay. Yeah, of course, you're there. So updates Stapler form 20 to 80, 39, 39 Java, okay. And it's specifically compatibility with the content security policy plugin. But I figured that's probably something important to note if it's gonna have to do with CSP. So yeah, that's all. Okay, thanks for that. That's all though. Yeah, that's good. Thanks a lot. Yeah, this should be good. There we go. Thank you, Kevin. Anyhow, it looks like we have covered all the subject had in mind, so that's a wrap up. Thanks a lot, Kevin, for your time. The video should be available from 24 to 48 hours and we'll see each other two weeks from now. Until then, happy Jenkins. Bye-bye.