 Welcome. It's the 27th of February, 27th of March of January. Wow, I'm way off January, not February. Okay, so let's fix that. Okay, only made a few times that mistake. So 27th of January. And it's Jenkins documentation office hours, topics, action items, Debbie and 12, Google summer of code, and we'll skip over requests of note this time. So on the Debbie and 12 without JDK 11 topic, JDK 17 or open JDK 17 will be available for for Debbie and 12. When it releases in April or May 2023, open JDK 11 will not be available for Debbie and 12. They're dropping it because Debbie and 12 life lifespan, I think will be longer than Java 11's end of support, they don't want to end up supporting it themselves after others have stopped. So what that means is the docs, SIG has decided that beginning in in at the release of Debbie and 12. We will switch to document Linux installs with Java 17, not Java 11. We will continue to support Java 11, but we want to have a single document that describes the installation process no matter which version of of Debian or Ubuntu Linux you're on and using Java 17 is the simplest way to do that. Okay. That's any questions there. So is it because like, it's backwards compatible. That's why if we have 17 seconds automatic works very long. Correct. So Java JDK 17 is already fully supported already fully supported with Jenkins has been supported now for many months. So, so this isn't actually any any all any change of support or anything it's just which one we document. Okay. And that has been since at least 2.361.4 I think it's even 2346.1. Okay. So it's not a this is this is only a change of documentation now upcoming. The day will come when Jenkins will eventually stop supporting Java 11. But that hasn't been decided yet. And I more discussion is needed. Okay. All right, Google summer of code. Let's take that one next. How would you like to approach it Chris. Maybe. Should we go through some of the like the project ID pages. Let's do. Yeah. Yeah, you go to Jenkins style. Yeah. So project Google summer of code. G start 2023 project ideas list. Okay, any particular ones you'd like to look at more closely. Maybe let's see. I think this time we should look at another one because like last time we looked at the alternate boot tools and the booting Jenkins. Right. We looked at last time so this time we may be a look at another one. Okay. We I mean we could do. We could do plugin installation manager tool improvements we could do something like that. I think there's it's probably better if we do items that I'm involved as a mentor. Yeah. Thanks area. Well screenshot automation. Okay. Okay, so I'm going to pick plugin installation manager tool because that one for me is while it's, it's approved. I think there's more for us to discuss and identify and consider. Right. So here for instance, what this just says is improvements to the existing tool, but does not suggest suggest specific improvements. Yeah. So let's let's look at some of those and see what they are. And I think we ought to extend the project definition to, to specifically highlight some of those tools. Some of those improvements. Yep. Okay. Now I assume we probably want a text editor so that we can write some words. Yeah. So let's bring up my text. Where did it go? Where's my mobile X term. My favorite text editing tool. Apparently I killed it. Okay. Okay. Here it comes. Add. Plug in. Install project. Details. Yep. Okay, so. And 2021. 2020. Where is our, well, maybe I'm going to have to go all the way back to the up top. Yeah, let's just do this. And we'll grab that page. Interesting. Content. Yeah. Projects. G sock. Yeah. Okay, just a minute. Okay. Content. Projects. G sock. Yeah. 2023. Ideas. Plug in installation manager tool. Okay. Here we go. Right. Okay. So now back to our back to our. Recommendations. Okay. So. Quick start clone the project, run the tests. Run the, run the tool for various plugin combinations. Yeah. Okay. We're going to try some edge cases to see what could be improved. Good. Okay. Okay. Right. So now. Back to our. Document. All right. So. It was created and it's been improved. And now it works well inside the. And there's the suggestion for some ideas. Okay. So. This one. This is actually a good first issue. Okay. And that's, that's something we can help the newcomers with. Of. Flagging things that are good first. Good first. Oh, whoops. We have a good first issue. Tag. Oh, okay. Oh, we do. Okay. Good. That's why. Yeah, I'm more accustomed to them getting that one right without me needing to refresh, but yeah, okay. So. Now. Add support for file protocol. You've used update the Jenkins war. Yeah, actually this list of enhancements. So this one, for instance, I like a lot. Okay. And I think it's a, so, so there. And I'm not sure I'd call it a plugins lock file as much as I'd call it a plugins.txt file. So, but. Let's, I would say we put that one in. And so. Key improvements identify prior to some plan, propose the areas for improvement, work with mentors to plan those improvements. Some candidate ideas. From the mentors. Include generate plugins.txt file from existing directory. That a fair way to say it. Yep. Okay, and we can price certain prioritize these later as we get. All right, so show progress bar while downloading plugins from plugins.txt. That one feels like a good one. Show optionally show. Show progress bar during download. Okay, then list. What is that. I'm not even interested in that one. Okay. Option which lists install plugins filtered by only the plugins. Not installed by another. I'm not, I don't even understand what they're asking requesting. So I know. Okay. Okay. Keep comments on the text export. That's an interesting idea. Okay. Is there a way to retain the comments and somehow associate them. Interesting. Okay. Retain comments. When. Creating new file from existing file. List skipped plugins. I like that one. Okay. So let's put the file protocol. Oh, that, that one was already, that's a good first issue. So we should probably put that into the, let's see, there's already. Yeah, here it is. Oh, yeah. Right. So it's already, it's already going to find that one. Okay. Support for the file protocol. We already talked. Yeah. CLC Li fails with incorrect plugin dependency minimum versions. No, okay. This is just a user misunderstanding. They're missing a flag. Oh, okay. Okay. Yeah, this is just the user is missing misunderstanding. You're okay if I make an update here. Yeah. This is a user misunderstanding. The. The plugin installation manager tool. Installs the most recent version of a dependency. Unless the. Unless the more most recent compatible. Most recent version of a dependency. Unless. The, and now I need to find the option just a minute while I bring my command line. Maybe option we need is. I don't know what the option is and conversion latest. Yes. Minus minus latest faults. Now wait a sec set to true to download latest transitive. Yeah, I think this is the one where we want, let's do, I could do a quick check, but I believe we want minus minus latest faults. Okay. Yeah. Those. All right. So back to our issue list. Okay. Proxy proxy basic off. I don't know if I'm not a big fan of proxies, but. That's a good one. Here's one, right? So this is a really good one. This one is split the command line to. Split the command line options to sub commands. So. And here it's. Let's get that in there. Okay. So. I guess I should, I'm not persuaded, add sub commands to the command line interface. Arguments options. Arguments. So, and this one. Requires. A design and. Definition of definition and design. Of the sub commands. And how they should work. Okay. And their meaning. Great. All right. So back to our list of possible issues. Here's an interesting one. Log the suggested mirrors for download. Okay, but I see no. No resolution on it. So, okay. Yes. So report the mirror URL. And download failure. And original URL. Okay. Yep. Okay, here's some discussion from Oleg on the idea from 2021. Specialization. Okay, so this is calendars with the zoom link. Okay. That doesn't help us. Okay. So no recording. Have wanted. Let me see if it's in the Jenkins. YouTube channel just a moment. Like it is right here. Okay, good. April 13, 2021. Okay, very good. So this is one. That's a good candidate for us to link to and even to embed. Okay. So we're going to go into the. Into that page, right? Because now I have, I need to watch it to see. But he's got. I'm sure their ideas there. Yeah. Okay. You're okay if I put that in as an embedded video. Yeah. Now, where would we put it? Here we go. How about here in background? Additional background information. Maybe found. In a video. According. From 2021. And here it is. I have to find the syntax. Just a minute. There we go. That's what I need. This magic. And then I replace. Few characters. With a few other characters. Okay. Okay. So we've put an embedded on that discussion topic. Very good. All right. And this one really. I don't see any reason to leave it open. I don't see any issue since the recording is available. At. Oops. There. Yeah. Close as completed. Okay. Good. All right. Yeah, this is, this is just a, okay. User wants something different than it actually does. All right. I do not fetch plugin versions easily. Oh, right. Okay. Interesting. Okay. So. That one, that one is an interesting one. Because. Docker containers. Have, have a specific problem here. Improve image caching for Docker container builds. And I'm not sure how you would do that because the cache needs to somehow be outside the container. Yeah. But, but I think it's an interesting thought. Okay. Option to ignore bundled plugins. Hmm. I don't, I don't understand the, the. The question. Okay. All right. So. We'll continue. I don't understand the proposal here. Okay. The current plugin installation manager treats requested and dependent plugins. Identically seems like that's correct. Neither are downloaded. If it's already installed and the required version is less. That's correct. But change to download a requested plugin, even already installed. Use the version calculated already using requested. Assuming that some plugins have dependencies or is it not? Plugins plugins do absolutely have dependency on other plugins. Yeah. You bet. And so what this is saying is. If I read this correctly, it's. There are duplicate downloads of the same plugin. But if a plugin is a dependency, so. I'm a little, I'm quite surprised. At that. So this, this one is worth testing. And seeing if that is in fact reality. So. Only download a plugin once. Once per session. Test if still an issue. There. Okay. Errors. It will exit the image. I'm going to talk to you. See, I think. Okay. My take on my, my idea on this one is. I don't want the plugin manager attend plugin installation tool manager to attempt to be a database. This is asking for rollback, right? And if you want rollback, there are other ways to get rollback. Yep. Okay. So I, I don't, I don't. Don't particularly want that one. Okay. This one feels like a reasonable one though. Right. Show updates for. Yeah. Allow security warnings. Worked. For. Only specific plugins. Okay. Only specific plugins. Okay. Or only specified plugins. Okay. All right now back here to where we were. So we've, we've been through several of these. Plugin manager is losing plugins installed in previous images. Oh, oh, this they want to. I don't understand if this is resolved. It's not obvious. Okay. So. Based on the earlier comments. That this is resolved in newer releases of the tool. Okay. I'm closing it. Okay. Good. Thanks for your patience with this Chris. Okay. So on to the next page of, of possible issues. Add option. Yeah, we, we've looked at this add option to ignore bundled plugins and I didn't. Get it. Okay. Next. Optionally skip plugins listed in plugins.txt on latest version. Close tabs to the right. Updating all current installed plugins to their latest version. I don't understand it. Okay. Updating all currently installed plugins to their latest version. Okay. So they're not current. I run this, they become. Okay. We have to check the update center. You need it. I don't understand that. Is there more information in the jury issue? Okay. So. So as it was resolved in this. Change. And that was resolved in 2019. So I'm closing this one. With what? Change number 44. Oh, you know what? I can put this. No. Why can't I. I'm in a milestone. Okay. So. Resolved with number 44. Here, let's make it easier to read. There. Okay. Good. And I can do that. Continuing. Support Maven repository. I don't understand this concept. HPI files are not in the Maven repository. Okay. So how will that help? At least as far as I know, okay. Double checking. Find. M2 repository. Minus name. Start at HPI. Oh, well, surprising. Okay. There are some in there. Yeah. Why would they be in? Huh. Interesting. Okay. Let's look to see how many of the get client. Okay. There are quite a number in there. Yeah. So not a bad. Not a bad idea. As a way to use another local, a local disc, a local cash. Right. This is good. Reduce downloads. Yeah. Okay. I think I understand what they're, what they're requesting. And this would add additional logging levels. Right. So for diagnosis. And allow. Read. HPI files from Maven cash. You have found there. And now that is an interesting. Okay. This one, I think I understand what they're, what they're requesting. And this would add additional logging levels. Right. So. Multiple logging levels allow. Logging to be increased and decreased. Increase for debugging and diagnosis. Okay. Reasonable way to describe it. Yep. Thanks. Okay. Some features are slightly fragile. Security. Oh, security warnings should be shown by default. Yes. I agree. Right. Yes. I like that. That's, that's a good show security warnings. By default. There we go. I feel like we've got a good list, Chris. Yeah, that's quite comprehensive or does quite a lot. Longish enough to start. Well, and, and there also some of them are a good, good thing for a new contributor who wants to try something to say, I'm going to try one of these. I'm going to try show security warnings by default. That's probably actually a good first issue. Yeah, I think so. So, so that's. Maybe what we do is put that one. There seems to be no real reason for this to be do things to save. I agree with that. Okay. Good. So I'm going to actually label it good first issue. Good. All right, Chris. Thank you very much. Welcome. Let's see. Let me submit this. Well, let's read it first just to be sure that I didn't make some terrible mistake. It's happening. Thanks. What's that? Is that an extra strike six after the last link you added? Oh, thank you. Yeah, right there. Okay. Link to the video. Remove an extra blank line. And then our list of candidate issues. Okay. Good. All right. And I'm going to take that one out because we made it a good first issue. All right. All right, so add video and list of the issues. Possible issues to. Idea. Plug in installation manager tool. Project idea. Needed. More, more details. Those details are now included. On the page. Along with. And embedded video. From. 2021 discussing. Enhancement ideas. All right. So let's first see that it looks okay for us. Run. So thrilled. You've been at connection. Implemented Ruby 3.2. And so it's, it's now running a modern version of Ruby. And a modern version of no JS and. So. Nice updates. All right. So, Mark. To this one. Come on. Answer me. There we go. It's here. Okay. Now. Sub projects. Sub projects. Google summer of code. GSOC 2023. Plug in installation manager tool improvements. Oh, that's tiny. That needs to be bigger. Yeah, is that so tiny? Okay. Oh, I didn't start it in my editor. Okay. Get grab video. Ah, there it is. We need to give it a height. Oh, okay. Yeah. Or a width. There we go. With the 640 center aligned. Extra. Yeah. That's much better. Now look at that. Yeah. That's a lot better. So I think we've given some, some additional ideas. Now I've still got a schedule a session with those who are interested. Friam, I believe said that Friam was interested in mentoring this one. And so I've still got to do that. But this gives us a good, a good start, I think. Okay. All right. Chris, thank you very, very much. Let's submit this pull request. Okay. So title should be. Extend. Plug in install manager. Project idea. Submitted. Thanks, Chris. Welcome. All right. I'm going to stop sharing and we'll call it done unless there are other topics you'd like to discuss. Don't think so. No. All right. Thanks for your time and thanks for your help improving it.