 Hello, and welcome to the Jenkins documentation office hours. Today is July 13th, and this is the EURUS edition. Today we have myself and Parquay, Bernos on some well-deserved PPLs, so enjoy that. Today on the agenda, I have a couple blog posts that were published this week. The weekly release and LTS release, both upcoming and future. There was a security advisory that was published yesterday. Google Summer of Code is in full swing. We just had the midterm presentations and some great check-in points from all of our participants there. The Java 17 transition, open call requests of interest, note on DevOps World Tour, and note about the next two Asia Docs Hours meetings. They are canceled, Mark's unavailable, so the decision has remained to just not have those. They have to be moved to the calendar, so for anyone watching this in the future, keep that in mind. Anything else to add to the agenda here, Mark, or does that cover things for you? A tail-end item that I won't be available for next week's meeting, but I believe Bruno will be, so I assume you and Bruno will meet. Oh, for this session, yeah. Yeah, this session next week I'll be out of the office. Yeah, yeah, of course, no worries, and yeah, I'll be hosting it no matter what. All right then, so first things first, for the blog posts, we just posted our June newsletter at the beginning of the week. So this is great updates from June, from the Jenkins teams, thanks to all of the SIG leaders for contributing their updates and getting this out onto the blog. And then we recently had an infrastructure outreach, Damian de Porto, who is part of the infrastructure team helped and managed that and has created a post-mortem kind of just going over what happened, their actions to resolve and background and some next steps for us to take as far as making sure these sort of things don't happen in the future, or if they do, what kind of actions can we take to mitigate that even better. So thanks to him for creating this and writing this up. And thanks to everyone that is listed here for all of their help and assistance in getting the results. So it looks like that was only four hours long. So that's a great and a grand scheme of things. Obviously, no downtime is passed, but that's often also a pipe dream. So good job. The weekly release of 2.4 and 4 for Jenkins was released successfully. ChangeLog has been merged in as well. The next LTS is 2.401.3. And that will be released in two weeks on July 26. ChangeLog and Upgrade Guide are present and available as pull requests right now. But we're leaving things open for a little bit just to make sure that any new entries or any other backwards can be added. The next LTS baseline discussion has been started in the developer mailing list right now. The discussions between 2.413 and 2.414, 2.414 seems to be the frontrunner at this time, it's got all the updates and fixes that we've had. And as of its release, there haven't been any issues or complaints. So things are looking up for 2.414. And that's a special thing to happen. And once we have that baseline selected, we'll share that. There's a security advisory published yesterday for plugins specifically. It's not JenkinsFore affected. And just something to be aware of is there are some unresolved issues down here towards the bottom of the security advisory. Just be aware of that. If you run into any issues with any of these plugins, there will be notification or warning regarding that. And if anything too, that they could be up for adoption, which would be a great opportunity to step up and take that on. If that's something that's really crucial and needed. If you find that it's something you're using a lot, it might be a good opportunity to join the open source community in a way. Also, just one last thing. If there are any other issues or if anything comes up, if anyone finds anything, please report them obviously to the security team. The more we know, the better we can do to help fix these issues before they get too far. So there is one item of note there. You'll see it. It's on your screen right now. There's the link to Rebuilder plugin. That's about three quarters of the way down the list. Rebuilder plugin is one that has been included in the Jenkins setup wizard as an optional but visible plugin. So when you run the setup wizard, you can choose to install the suggested plugins or you could take the alternate path and choose your own. And in the choose your own, it lists the rebuild plugin. Now that it's got an open security advisor against it, the pull request has been submitted for proposing to remove it from the setup wizard and 2.415 and to backport that to LTSs so that we're not suggesting to new users that they should install a plugin with a known unresolved security vulnerability. Now, it's got a larger number of installations. 49,000 installations is a lot of installations. So we would much prefer it be adopted and somebody fix it. But the reality is right now, it's got this security vulnerability so it'll be removed from the setup wizard. And is there a chance that in the future, is these issues are resolved, Mark, that it can be put back in? Or is it? Yeah, that option's available. Certainly there's nothing stopping us from adding it again to the setup wizard. It just doesn't make sense to have it in the wizard when it's got a known vulnerability. Right. Thanks for adding that in. Appreciate the context, Mark. Thank you so much. Up next, so Google Summer of Code is something that's been going on now since May. The midterm presentations were completed just last week. Huge thanks to Vandit, Jagri, Harsh and Shatash for presenting and sharing and all of their work on this. The recording is actually available here in webinar. And so it's about an hour and 40 minutes long, maybe roughly maybe a little bit shorter than that. But so much great, great content, great insight. And just a chance to meet the participants, which is really, really nice and puts a face to this, which is really lovely. Lots of updates, lots of great progress is made. The midterm evaluations are also due from the lead mentors by tomorrow. So I've met a chance to, by all means, make sure you do that. But that's something I'm sure everyone's been working on anyway. So for Google Summer of Code, one of the projects is the Docker QuickStart project. So this is the one that Harsh is working on. And during the webinar, it was his first time presenting to a group in an online meeting, did really well, shared some really lovely and really great insight to the project and what he's been able to accomplish so far. And you can actually see his portion right here. Mark and Bruno also submitted some requests to provide various updates and tests, which is really great. This is the idea of Google Summer of Code is that new contributors can work with experienced developers and experienced contributors to just build their own and get that within the door and leverage and understand open source and in this case Jenkins, in our case Jenkins. And then Vante has been working on the building Jenkins.io with alternative tools projects. So they're using Antora and have a prototype site that has been built in, is displaying a lot of the visual updates and differences that would be, that would exist in a different version. Nice thing is here too. And one of the big things is that it's version documentation. So you'd be able to switch based on the version of Jenkins you're using LTS weekly. So Kevin, would you be willing to test drive it? In the bottom left corner, there's a drop down for 2.2. I think if you pick 2.1, it will switch to documentation for 2.1. Good. Okay. So and that is working. That's good. I hadn't had a chance to test it. Yeah. And it looks like there's also another one up there on the right-hand corner too, Mark. So multiple points of access, multiple ways for people to navigate. But yeah, the documentation site is working really well. It's color coding and shading things a little differently to offset that better. I think this looks a lot nicer and a lot cleaner as far as just the presentation of the documentation itself goes, which is great. And then I know that there are, I'm trying to think of where they might be, but there are examples of code blocks and warnings and notes that are all visually updated as well. Could you click on one of the really long sections like installing Jenkins over on the left? Okay, it's fine. And then do, let's see, it was managing Jenkins, I think that is also long. And again, doesn't look bad on your screen. Good. Okay. So much better than the vertical scroll bar that we get on the left today. Very good. Okay. And show me pipeline, I think it is, is the other one? Yeah. Okay. And then managing Jenkins. All right. And system administration, the very last, the second to last or third. Yeah. Okay. Great. So this is definitely rendering much better. Yeah. And I, something I just noticed here, so even like the subsections are collapsed and uncollapsable, which is not the case currently, you have to actually click on the reverse proxy configuration link to then see the list of multiple proxies. So this is, this is great. So yeah, looks awesome. Big thanks to Vandie for working on that. And again, all mentors, all of the org admins, everyone that's been part of the Google Summer of Code experience, none of this is possible without you. So thank you to literally everyone working on this. It's, it's incredible. So, and just one last note on the Google Summer of Code, Djigrude has actually written a blog post talking, describing a lot of her experiences thus far. That's actually, that should be ready to merge once she's gotten a chance to check my final review. But it's minor stuff. And yeah, as soon as she's ready, we'll merge that and get that published as well. So thanks again. The transition to Java, using Java 17 and the Jenkins documentation has been underway for some time with the Debian release of W12 and no longer offering JDK 11 or delivering JDK 11. We've been, I've been working on making sure that our documentation matches that and uses Java 17 as our examples, as our image containers so that when people are seeing the documentation, that's what they're going to be encouraged to use. Java 17 is fully supported by Jenkins at this point in time. So there's no reason not to. It provides better and more testing and just better and faster development environments than Java 11 does. So I've been able to go through the documentation. At this point, I've gone through the, what I would call regular documentation. So things like the installation documentation, the pipeline documentation, using, managing Jenkins, those types of documentation. And have gone and updated them accordingly. So far, these are the ones that I've found that needed updates and have received them. Mark's gone through and verified all of these as well and has helped me with testing and making sure that everything is correct and valid. So everything's going really well right now. We've made a lot of headway right now. The next step is tutorial pages and making sure that those are all set and making sure that we have a page similar, if not exactly like the Java 8 to Java 11 upgrade instructions. Right now, that's still valid. We want to make sure that's still available, but we do need more before the Java 11 to Java 17 transition as well. I started working on that. Found some gaps there and some things that we weren't aware of at the time that might need a little bit more guidance and clarification on, but that's something that I will be sticking up with. Mark and others will be changing. Moving on. So a couple of pull requests of interest that we have open right now. So as before, we have the pull request from Tanu about administering Jenkins on Kubernetes. He's added some more content. There's a lot more here. We just need some confirmation from subject matter experts or if there's anything. Could you jump to the bottom of that one? Because I wasn't sure that Tanu's had made any changes since the last time we met. So whoops, you're a little too far down now. So up, whoa, right there. Perfect. Okay. So two weeks ago was the last change. Okay. So Tanu's has not been active on the pull request since our comments and corrections. Great. Okay. And that's up to Tanu's. If Tanu's wants to be involved or not, that's not something we can force. So we've provided the feedback and now it's up to Tanu's when or if they get involved. Great. Okay. Perfect. Thanks, Mark. Appreciate it. Next up on the list. So Jeffrey Chen originally submitted the pull request for moving the best practices page from the Jenkins Wiki to Jenkins.io. So we've been working on this. Mark's converted a lot of it here and has put together our best practices page that we feel is really well done at this point and recognizing that best practices are from our discussion to be had, not hard and fast, walk locked in place sort of thing. The best practices page is what has been found and worked really well and what we recommend and even if it's not 1 million percent complete in that sense, where we're at is really good and solid. We have a lot to share. Yeah. I think Kevin, scroll to the bottom. Let's see if the preview is ready. It may not be ready yet. Okay. So we'll scroll up a little up just right there. Okay. View changes, view deploy. Okay. So the deployment doesn't have the fixed type or link yet. Okay. So maybe we come back to it before end of meeting or visit it later. I think it's ready to merge if that last change was successful. So if the broken hyperlink is fixed, then I think it's at least better than nothing and one more wiki page that's been converted and converted in a way that we think makes sense. Definitely. And we do have the preview for the best practices page that we had right before that making change. So a lot of free contents already been put here. A lot of videos that Darren Pope's taken the time to record and make for us that just really does an amazing job of helping explain and clarify some of the Jenkins in open source ideas that could be, that it would be strong for someone or just something that's a little bit more foreign. This is great. And yeah, once that fix is all done and this is ready to deploy, we can check it out and go from there. Next up there is the scripting and security page full request. I have not had a chance to look into this. No progress on this one for me either. And I won't have a chance to discuss it with Meg for another three weeks because I'll miss Asia office hours 12 hours from now and I'll miss Asia office hours a week from now. So the next time Meg and I will talk will be two weeks from two weeks and about 12 hours from now. And in that time, Mark, I'm sure that I can look at it and get something put together at the very least. So I'll do my best to get synced up with Meg on that one too and make some comments or something. I actually wouldn't worry about it, Kevin. I think the Java 11 work is much higher priority. This one is work that Meg and I had started. We'll just keep working on it. Okay, fair enough. No worries and I'll keep on doing that. Next up. So DevOps world tour this year is a little different. So registration is open right now. And the idea behind DevOps world this year is that it's going to be multiple smaller sessions globally as opposed to one larger conference in one location. The idea is that this will be able to reach more and more people give flexibility in terms of dates and being able to connect and go. And there's going to be Jenkins representation and talks. We're figuring all of that out still. So nothing really to note there yet, but registration is open. You can check out on the site what locations look like, what the dates are. So New York, Chicago, Silicon Valley, Singapore, and London. So this is going to be really great, really fun and hopefully this will make it a lot more accessible to folks since it does have that reach. And I am pleased to say that I'm on the agenda. For now, if you looked at the agenda published now out there for New York, for Chicago, and so click the New York one. And I think they've got the speakers listed. There they are. So I'm on the agenda for New York, for Chicago, and for San Francisco on the topic. Benefit your business by contributing to open source. Then was it, what was the third one, Mark? Or are you just doing New York and Chicago? New York, Chicago, and Silicon Valley, San Francisco. You will be at this. Nice. That's awesome. Exciting. So there's plenty of look forward to there and plenty of reason to go. Just to hear, if anything, to hear Mark's talk. And then again, as we mentioned at the beginning of the hour, Mark's going to be out of office for this evening, today, tomorrow's Asia Docs Office hours and next week's as well. So the next meeting for Asia Docs Office hours will be July 26. Okay. And that covers everything I had on the agenda for today. Mark, anything else to note or scroll a little quickly? Nothing else for me. Let's see if this now has the deploy. Well, it does the deployment. So now. It works. Okay. Perfect. I think it's ready to merge then, Kevin. All right then. So I'll go ahead and merge with that. And the best practices page will now be available. It will be visible on the dig in the site in a couple hours. Fantastic. Thanks. Thanks so much, Mark. A great day, everyone. Recording will be available in 24 to 48 hours.