 Okay, and hello and welcome to the Jenkins documentation office hours today is September 14th This is the EU US edition and today we have myself and bring over rock bin Mark is in joining us today since he's at DevOps world tour. And so Anyone else joins up? We'll welcome them as they come in and for now. We'll go over the agenda And so on the agenda some updates for Google Summer of Code Just check in on the process of choosing a plug-in bomb The Java proposal that mark has been working on and we've been discussing the addition of the platform information section Just a note on DevOps world tour and some housekeeping stuff because mark is at DevOps world tour Docs office hours Asia are canceled this week And you can see here, they even discussed it last week at the Asian Docs Asia Docs office hours So that will not be happening later today Yeah, anything else that needs to go on the agenda or does that cover? I don't think so. Thank you, Kevin Okay, cool So first things first so Google's come Google Summer of Code is getting to the end of the timeline So the projects for the most part are complete and we're just waiting on blog blog post recaps for many of them Just to go through them individually. So for the doc compose for tutorials The project is complete. It does need some more work to deploy and be included in documentation But it's completed. So really great to hear there And could use some help from the infantry Infra team which might be something they are able to do during Hectoberfest But we'll figure that out when you can sign to Hectoberfest To be determined on that front The versioned site for Jenkins.io from Vandit is going amazingly well It's still being worked on it's still being developed, but they've done a lot of work since the last time we checked in with them They've fixed a lot of the links that were there. They've updated a lot of the just kind of the front end there And then they're using Gatsby as the front end and GitHub for both for review and so The pull requests are arriving the blog post layout arrived last this is last week now for Chris and Yeah, it looks like it's on track to complete a couple weeks. So Looks like everything is going swimmingly there final layout still under development and again, they fixed a lot of the linkage and navigation that was not working or Leading to the incorrect places last time. So great work there. Thank you again to Vandy I get lab plug-in moderate modernization still being still being worked on They need some more testing to compare all the new behavior, but things are going well there And then the plug-in health score. So Djigrude's posted a couple of different blog posts to recap the different probes that they've gotten launched there is one that still is pending to be merged and The rest are on the Jenkins blog So check that out and I think a couple of them were actually called out in Last week stocks office hours. So the number of open issues probe the dedicated the deprecated JSR 305 imports probe And then there is the one that still needs to be merged But thanks to jacuzzi jacuzzi for writing all those up The one that was merged does and one never had a couple comments on it. So that one does need to be Re-examined just to see if those comments are applicable. They seem to be pretty straightforward feedback about what some extra context that could help in terms of using the abstract that jagrude was using and Just some context to help the readers understand a little bit more about the background of the probe. So We'll follow up there But yeah, again plug-in health score is reaching going toward the end of the project Adrienne has returned from holidays guidance and Yeah, it looks like the oh the final presentations happened earlier today Bruno. Is that correct? Yes, we had great presentations and demos earlier today all went fine And I'm pretty happy with the results of this season of G stock for Jenkins. I think the progress are Amazing frankly, I'm really proud of what the contractors managed to do this year. Congrats to everybody mentors and contributors Of course admins. Thank you Jean-Marc Alissa and Chris for the amazing work And Bruno, but that's okay I was just a mentor, you know, I'm a wannabe admin I should be admin next year This year I was building my muscles, you know most of the time I was just looking at how things get done and next year that will be my my turn just into the regional I Just lost the wording. I'm done. Anyway, yes And just a few words about Ashwater's project He came to the Jenkins infra Meeting this week and Damian Gipolto took some time to explain what was needed to get His work integrated into Jenkins and for our Jenkins CI organization, you know As you know, we have a chicken and egg problem We can't modify the documentation pointing to the Ashwater's private not public but own Repo, you know, it's not part of the Jenkins organization. So Damian gave a roadmap list of things to do So now Ashwater knows precisely what he has to do before his work gets Integrated into the Jenkins CI or infrared condition and then we'll be able to make some PRs to modify the existing But at least we've got something to chew on that's pretty cool That's awesome. And that's the Docker compose project correct Bruno. You're right. Yeah. Okay. So I'm sure great Fantastic and the recording for the Jenkins online meetup will that be available later? Yeah, later on today. Maybe what worse tomorrow morning. It will be on the meetup page for this Event and of course on community dot Jenkins dot IO Right. Cool. Just want to make sure that the reporting will be available at some point not yeah No rush on that obviously, but yeah, just to make sure that For anyone who's interested, they'll be able to watch it back later and see the presentations. So really exciting great Anything else on the Google summer code to discuss Bruno or does that cover a thing? No, thank you. Okay. Great So next step on the agenda so The process of choosing a plug-in bomb. So this was started as a discussion in this pull request A user Kyle had submitted This issue saying, you know, hey like what How do we know what which version to choose? Is there A way that we could determine which version is For what purpose or just to make this process clear for users for end users And so there's been some discussion here Mark provided some static examples that we could have so stuff like the last Jenkins LTS to support Java 8 first one to support Java to require Java 11 most current one so just stuff like that but and potentially using the update CLI to do those updates and include and Kind of facilitate those updates accordingly Um, there hasn't been any progress here. Uh, since we had started talking about it a couple weeks ago I'm likely not to be more progress due to other priorities coming up, but This is something that is happening currently in, uh, the Jenkins repo. So it's Uh, definitely worth discussing and further considerations Yes, uh We'll be glad to see the output of the discussion because as Jenkins end user I was often puzzled By which version should I choose and why and frankly, I think the documentation does not exist yet So that will be something nice for me to read And uh, yeah, and and mark had actually included something like this for the improving a plugin tutorial So this it does exist it is there, but there definitely could be some Um, enhancements to the documentation to make that more clear for users There is uh, some slight inconsistency in the improved plugin tutorial when it comes to choosing the bomb because in some places like you are showing there It's 2.375 and in some other places it's a 2.387 And you just don't know why it's like that right And so, uh, this sort of thing would help to alleviate that issue kind of just get rid of all the questions at that point And make it nice and simple and straightforward for users to understand which bomb they should be using Yeah, thanks a lot for the user who raised this issue because I was I've been puzzled several times, but I haven't taken the time to raise an issue about that I should have so thanks a lot sfcgh Cleon hold for that issue Yeah, I think uh, I think his first name is kyle. So Uh, thank you kyle. Yeah, just to make like easier. I don't know how to pronounce that any of these things So but yeah, uh, so great to have that. Thank you again And uh, yeah, so more to be done now Uh, and then so uh, next up on the agenda. So the java support and kind of just Java for jenkins proposal that we've been discussing marks been putting together. Uh, so There's the existing google doc where we there's all these potential options here Uh, some things that have been included and updated this trend this transition to a two plus two plus two java support um, and so Uh, the idea is that this would help line up with The way that java is doing its own releases And so, uh, this diagram Visualizes explains a little bit better. But so So we have Java 11's availability jengens on java 11 when it was required oldest supported Uh, and just how we can support java going forward for the for t-ball future And this is you know, this is looking at all the way up to java 33 and you know 2020 and 2034 so We're looking out real far. But the idea is that this would help to align Jenkins and java support. Um, it also coincides with how support is handled through the The vendors themselves and and other Uh, operating system select windows support um, linux support stuff like that and Yeah, and then uh, and it also goes into Stuff like when we start to Uh, notify users that java 11 isn't is heading towards end of life. So getting that an admin monitor working Uh for the java process as well as os And then yeah java 21 is uh already being worked on by the infotain to include in jengens Uh, it's going to be the preview function the preview Version of java 21 is available currently. Uh, and when java 21 is properly released in, uh Jesus like less than a week at this point. That's five days to go. Yeah So, uh, our goal is to have java 21 supported in jengens, uh by octo by october 23rd or so is roughly the uh Goal timeline. We've given ourselves. So Um, but yeah, things are happening really quickly. Uh, this has been Being worked on by a lot of developers and engineers. Um, thanks to you basal crow. Thanks to damon's a portal Ervela mirror stephan Who I forget stephan's last name right now Stay fine. Yeah stephan male Because uh, I got another email from a different step Uh, just thanks to everyone that's been working on this and testing and creating and uh, testing with getting java 21 into the jengens core it's going really well so far and is really huge in Getting this this java proposal off the ground the way we want it to Yeah, uh team jack almost you also worked on the jdk 21 and I think it was the first to propose to have jengens contour image with jdk 21 beta version And this week I saw a new contributor to jenkins appear and make a proposal What about having an agent a jenkins agent using jdk 21? And he has done the the pull request after raising the issue and Kenneth Salerno has also worked on that. So now we have the three jenkins agents available for jdk 21 for arm v7 s3 90x ppc 64 le Arch 64 and also alpine Arch 64 So yes, even the community wants to see jenkins on jdk 21 even with docker That's yeah, clearly That's awesome fendt amazing. I yeah, there was more people than I even knew working on this stuff and even more that I didn't I still don't know working on this stuff. So that's really incredible to hear and Super encouraging that everyone's really excited about it and wants to see it happen. So that's great. That's amazing um, and uh, yeah, just just fantastic to hear and Actually see in action. Um, you know, this is a community effort and it's being done really I mean really wholeheartedly, which is nice um, and then In addition to this, uh, I'm going through the documentation Um to make sure that this all works with 20 java 21 Hmm And so right now I'm going through the guided tour everything seems to be going well there There's the node j s the python and the maven tutorials as well, which we need to go through but Yeah, for the most part Everything's going okay there. There are some documentation needs for the java 21 that are similar to the java 17 doc needs so uh, thankfully it won't be That thankfully we'll just need to add some documentation there and adjust the existing documentation Um, but yeah, just making sure that the tutorials and a lot of the instructional information is working Anything else on the java? Topic Bruno No, thank you. Okay. Okay So the next step so uh adding the existing requirements support policy documentation to the assistant administration section. So So I've created a new chapter for this called platform information We had uh mark had taken it to the doc's office hours asia to get some review and and uh triage because I was having a couple issues They were able to figure that out mark submitted some pull requests to my repo to get that all cleared up So now it's properly, uh, organized and I found the Missing piece that I didn't have and now it works I need to update the index page text itself because uh, I had initially just put some Placeholder text in there while I was trying to make sure it was working Now that it is working properly. I can do the rest of it. So Yeah, so everything's looking good there. Um, I've got the next steps for that and I just need to get the text put in So, um, hopefully I'll have that pull request created within the next week or so Uh Next up. So devops world tour has officially started out of this week. Uh, yesterday was the first day today is the second day and uh Between yesterday and today. So that's the new york session Mark is currently there giving a talk. Maybe it's already he's already done his talk But either way he's in new york hanging out at devops world tour And there'll be after each devops world tour Session day event. Uh, there'll be a jankins after hour session You know, let's talk about jankins That'll be held after each conference and um, yeah, it'll just be a nice opportunity to talk jankins with Mark and whoever else might be attending And then we also have the singapore and london locations where uh, libya, libya elami and tim jacombe will be speaking respectively We just published a really short blog post about it. Um Just to give you a quick intro to who's going to be there and what the what the deal is Um, and that what that let's talk about jankins uh deal is so Um, just a nice little intro here, but uh, yeah devops world tour is currently happening If you have not registered yet and still want to attend there are several locations and dates still there um And you have a couple weeks until chicago silicon valley singapore and uh thankfully london is until the end of November so plenty of time to still register and attend Uh, and then the last thing I had on the agenda again, just a quick house keeping note Uh, docks office hours asia is canceled this week since mark is at devops world tour Uh, so anyone attending then? Well, you don't attend just don't there's nothing to attend at that point One very last thing before we wrap it up I think there is a newsletter draft Going on for the august months Um, of course, it is much shorter than what we have the other month because of course During august people go on vacation. So not so much happened during the august months So there will be little to You know little to read, but that's okay Yeah, no, it's a great call Bruno, uh, I saw the draft and I remembered I have to go through it Uh an update my section a little bit. I think there was an update but um Yeah, the august newsletters Currently pull requests in the jenkins repo. So that um, yeah, we just need to get that up And that hopefully we'll get that published within the next few days Yep So, uh, yeah, no great awesome. Thank you very much bruno for uh, you're welcome calling that out Uh, and that covers the agenda that we had for today Anything else to discuss throughout their chair or does that cover everything bruno? I think you covered everything. Thank you kevin. Yeah, cool. All right, great. So then um, we'll go ahead and stop the recording here It'll be available 24 to 48 hours Thank you for joining as always and until next time. See you then Bye