 Good afternoon. Welcome to your Jenkins documentation office hours. Today is July 27th. Let me just fix that. And today we have myself, Bruno Rockman and Mark Wake join us. And if others come, we'll welcome them in. For the agenda today, some blog posts have been published recently. The next LTS baseline discussion has been started. Some just notes on the weekly and LTS release we had yesterday and Tuesday, respectively. Security advisory that was published yesterday as well. Just notes on Google Summer of Code. The Java 17 transition for the documentation. Some open pull requests of interest that we've discussed previously. And finally, DevOps World Tour. Is there anything else we need to add? Or is that coverage? Nothing for me. Okay. Thank you very much. So first things first. So, again, the blog post. So, Jagruti has been participating in the Google Summer of Code and she's posted and created these blog posts describing and providing some more insight into probes that have been getting worked on during the Google Summer of Code. They were all published respectively in the last week or so, week or two. But, yeah, they've just provided some nice insight there. And then we also have a full midterm recap for Google Summer of Code from all the participants here. So they've got their own respective sections and providing some insight into what they've been working on. Really great info. And this goes right along with the midterm presentation that they just had recently, which you can find the recording in the slides here. Next item on the list here is the next LTS baseline discussion has been started and has been making progress in the development mailing list. Right now, 2.414 is the frontrunner. Many people are supporting it. Jimmy Combs accepted that as far as what we can use. And there have been discussions about some security issues or back ports that need to be made into this. So the discussion is happening. Alexander Brandis is going to be the release lead. So thanks to Alex for stepping up and taking that on that role. And the change log and upgrade guide need to be created, but that's something I'll be working on in the coming days. So that should be where she might be in a good place. And then the discussion and everything is happening really well. So we're doing pretty well there. Next up, so both the weekly and LTS release this week were security releases. So the change log was published by the security team, and they made sure to include the security advisory that was published as well. So this was published yesterday. And the security advisory affects both plugins and Jenkins Core itself. So this is important to keep in mind and be aware of. Next up again, so Google Summer of Code is making great progress. We've reached a halfway point and we are now heading into the second half of Google Summer of Code. So figuring out the rest of the way, what next steps have to take, and any kind of pivoting or any changes that are happening are all being done in the best interest of the project and the progress being made. Next up, so the Java 17 transition is something that we've been discussing and working on for some time now with the Debian 12 release back in June. OpenJDK11 is not delivered, so we've transitioned to using Java 17 and Java 17 supported images in the documentation. So for things like the installation documentation on Linux, specifically because it uses Debian, we've updated that to now use the Java 17 and corresponding images. So Eclipse, Timurin 3.93-17, etc. So this is happening. This has been going on. Thanks to everyone for helping out with this and proving and getting this really well taken care of. We also have Java 11 to Java 17 upgrade instructions as its own separate page. So this is available and includes a really nice walkthrough that Darren Pope created for us that walks you through that process exactly. Working on tutorials right now to get those updated. For the most part, it's formatting and making sure that everything is aligned, but at this time, I've only completed the building a Java app with Maven tutorial. There are others that still need that review. And the last piece that still needs to be updated is the Windows installation instructions here. The reason being is that the Windows installation instructions are majorly outdated compared to what we're using for the rest of them. It's showing Jenkins 2.263.4. The only complication I've been having is that I don't have a Windows machine, so I've been trying to use VMware and other alternate options to try and get it working. I haven't had too much trouble, but that one's a little bit beyond my basic skills at this moment. Okay. If ever you want some help with that, I could help because I have a Windows machine. So let me know if I can help. Yeah, no worries, bro. I asked them. I tried to find out if there would be a possibility of me potentially getting a Windows machine that I could use for these specific scenarios, but I'm still figuring that one out. We'll see. They have some alternative options, but I wasn't aware of where to go for some of them. So I have to follow up with IT and just talk to them about it, but yeah. Cool. And then one of the other items that I'm working on for the Java 17 transition is also a blog post announcing this. The transition has been happening behind the scenes and getting the documentation updated. I want to make sure that this is not surprising or alarming to anyone. So I'm working on that as we speak, and I'm sourcing through the Oracle release notes and other various posting blogs pages that have been going through and comparing contrasting Java 17 to 11 so that I can provide some good insight and some ideas as to why Java 17 is preferred. Next up, some open pull requests of interest. So these are ones that we have discussed previously. The Jenkins and Kubernetes pull requests just needs Kubernetes expertise review. The scripting and security page, again, this is at a point where we can work on it further, but it's a little bit lower priority at the moment compared to other projects that we're working on, other tasks. So we want to keep that alive. It's valuable. That page is really important, and it's coming from the Wiki. So it's got a lot of information that is relevant to Jenkins and just needs some more love. And then this is something that we actually discussed last week, and Bruno added it in, but it's a pull request that Bruno had written to add the update CLI. We were talking about it and kind of using examples last week with the different versions and different, I guess, trying to remember what it was specifically about. I want to say it was one of the places where the Java 17 transition hadn't happened yet, but we know that it will need to be updated or one of the other versions will need to be updated again in the future. So Bruno was explaining kind of how this would actually help with that and how this could benefit just long-term usage. We already have renovate and dependabot. So there are existing cases of something like this. Adding this one would be just another one on top of that to help support us and any Jenkins users. Yeah, thank you, Kevin. I hope it could help. So for me, it's more or less finished with the latest feedbacks from Damian, for example. I made the latest adjustments. So now the goal is to have people vote so we can know if we should merge it or abandon it. And I say that a few weeks from now, I don't know if it's a regular thing to do, but we could merge it or close it depending on the results of the votes. And is there a specific comment or anything on here that we should be voting on? Oh, sorry. Yes, the comment where I say, please put a thumbs up or thumbs down. Sorry for not being clear with that. It's earlier in the talk. Yes, sorry. I was thinking that it was done at the time I wrote this comment, so I didn't expect more comments to blur everything out. Sorry about that. No worries. So the first message is somewhere in the comments. Okay, but there is a specific one that we can vote on in this case. Okay. Yeah, let's see. It's after this one, maybe. Yeah. Okay. I mean, I know there's a lot of stuff here. Find it somewhere. Okay. Got it. Okay. Good to know, Bruno. Thank you very much. Thank you. And then the last item I had on the agenda for today is DevOps World Tour. So registration is open right now. It's different from the last time we've done it. DevOps World Tour is now a multi-date, multi-city event. So this is more flexible and a little bit more accessible for people globally. It's not all lumped together in one location for a handful of days where it might be harder for other people to reach. So this is done in an effort to make it more welcoming, more accepted, more accessible, and just provide folks with the ability to go to DevOps World Tour in the backyard if they feel so inclined. There's New York, Chicago, and Silicon Valley for the U.S., Singapore, and London are the international locations respectively there. And Mark is actually going to be at the three U.S. event dates and giving a talk. So lots of reasons to go and see everything, but Mark being there is enough reason to go and see the Jenkins stuff. His talk is called Benefit Your Business by contributing to open source and essentially just explaining how contributing to open source really does help and impact the company and just what kind of results you can expect from contributing and utilizing open source and from communities all. Registration is open for DevOps World Tour, so feel free to sign up and let me feel like it. But yeah, the DevOps World Tour page has a lot more info and ideas and updates about what's going on and what'll be happening. So is there anything that's all I had on the agenda for today? Yes, sorry, Kevin, I remember something. Once again, it's newsletter, monthly newsletter time, sorry. So if ever you have a section on the document, feel free to enter your information whenever you can. Okay, thanks for your help. And second time, we talked a little bit about GSOC. I will try to be quick, fast, and not to spoil too much. But I know Mark was a real stakeholder on one particular function, which was get rid of the bash files so that we can only use Docker compose something instead of flunching bash files, which won't work under Windows, of course. And we have PR almost ready to merge that works without these infamous bash files. So now for lots of platforms, we can already type Docker compose up and it works. I'm still having some trouble under Windows for whatever reason, but we are investigating so. Okay, great. Good to know. And if you'd be able to share the link with me, either like after our session after the office hours are over, Bruno, I just so I can, excuse me, add it in here or just keep track of it in general. Yeah, of course, we'll do so. And I think Ashutosh will join tomorrow on asias.office hours. Maybe we'll make a demo. I don't know. I hope so. We'll see. And we'll have to discuss because earlier this week I discussed with Mark about when and how should we integrate Ashutosh's work into Jenkins.io or Jenkins somewhere. It's not ready to be integrated yet. But maybe one of these days we should discuss, should this be part of Jenkins.io directly? Should it be another repo somewhere? I don't know. Yeah, I mean, that's, I would say, I don't know what would be, I mean, I'd have to go through and read up on Ashutosh's project that you're working on. This is part of? Of course. And on top of that, I know there is the other GSOC project that is about rewriting the whole Jenkins.io website with Antora and the other two. I forgot the name of. But I don't know how much we can integrate files from elsewhere with Antora. I know it's pretty limited for the time being with what we are using. I forgot the name of what we're using now. But I think we can include, yeah, right, spot on. I think we can include some files which are part of the repo for the time being, which is already nice so that we could get samples, code samples directly taken from code files. That's the first interesting step. But if ever the code we use for the tutorials was taken from another repo, would we be able to include the code directly into the Jenkins.io building? Rockflow. I don't know. I don't have the answer. Gotcha. Yeah. And these days, I'm using more and more Git sub modules. You know, you have a repo and then in this repo, you declare that you depend on another Git repo and then somehow magically, whenever the remote repo is updated, then you get the updated version directly in your own Git repo. So maybe we could have a sub module to include Azure. I don't know. We'll see. Sorry, maybe too technical for documentation office hours. I don't know. It's good to have, even if I'm not 100% sure of what that entails, it's still good to know about. And it could affect documentation down the line. Like, these are all relevant, even if it's not... Yeah, these are all relevant. Don't worry about that. Okay. Thank you, Kevin. But yeah, no, and I've seen the work that Bundy has been doing on the alternative build tools for Jenkins.io and it looks really, really good. I know we've shown it here in office hours a couple of times. So it's not unfamiliar, but yeah, I mean, if there's multiple ways to get all this work put together or integrated into Jenkins.io, and the progress being made so far is really awesome. So if we can get that actually integrated, fantastic, even if it's a slower process than we'd like, or just making sure, like you said, making sure that the files and everything can be done the way that we're intending and hammering all those or finding all those weird little inconsistencies and wrinkles that we might not have seen. So yeah, I can imagine it's not as straightforward and as simple as, you know, you would think, because that's how everything always is. But no, that sounds really exciting, and I can't wait to see what we're able to do with the Google tunnel code projects and like their works. Thank you, Kevin. Yeah, of course. No worries. Thanks for sharing all that. So that covers the agenda that I have here. Just as a quick note, so Mark is back. You might have seen him earlier, but that means Docs Office Hours Asia will be back on for this evening. So you'll see him there. Outside of that, I think we're going to wrap up here. Video recording will be available in 24 to 48 hours. And until next time, take care.