 Welcome. This is documentation office hours. It's the 5th of May 2023. We're in the Asia section of office hours topics. I've got pipeline steps reference damaged. Google summer of code. Community feedback suggestions transition from Java 11 to Java 17. Early end of life notifications and early end of life of sento seven. Anything you want to add Chris. Nope. All right. Okay, so first topic is that we've got an unfortunate, and it seems to have happened within the last two or three days. Unfortunate damage to the plug in the pipeline documentation. So if I look here at the checkout step, this nested choice of objects should have a long list of many things in it, and it's empty. And there are a number of places like that where something that previously had content doesn't anymore. Right now, I'm attempting to run a bisect trying to find it. And we discovered during office hours Europe that it appears to be the pipeline steps doc generator, and some recent change to it and so the bisect is running pipeline steps doc generator through a series of checking different, different commits to see if this is the one that collapse the size of the file or if it's the next one, etc. Okay. Any questions there. Not really, but do you have, do you think we should post a link to that, like, to the post a link to the issue or to the maybe to the issue, or to the like the actual repo. Yeah, I'm not, I'm not sure what, how, how are you thinking that would help so what we've got is we've got a bug report that says hey there's this bug. Yeah. And I guess I might be able to. Yeah I'm not sure what we would do so tell me more about your idea I should listen rather than talk. We're going to show in here. Maybe like anyone interested to try to help. It's the one to. Oh, okay. Well, so here I can, I can certainly post a link to the issue report so the issues right here. And, and so issue. And it's got my notes in it of things that things that we've discovered we found that older versions of the doc generator created a much larger file than the new ones. And the bisect is trying to identify which which commit did the damage. Okay, is that what you were thinking did I miss something that you were suggesting. That's it. Okay. Yeah. All right. Okay, yeah. Someone might try to like reduce the error as well. Mm hmm. Yeah. Good. Very good. Thanks for the suggestion Chris. Anything else on that one. All right. Next topic then was Google summer of code. Chris, do you want to give an overview? Yeah, so like this year for 2073 we got four projects selected. And I think all for contributors of India. So, is that the. So we have a project so maybe yours is like that organization. Yeah. That's a harsh thing. Yeah. It was Docker for better. Better install tutorials, etc. Right. Yeah, I think it has a quick start in his name. Oh yes Docker Docker for quick start. That's right. Thank you. And here we can actually just read the blog, can't we? Yeah, we can just go. Here's get that plug in modernization building Jenkins that I owe the one that you and I will be mentoring together that Chris is the lead. Yeah. Let's see so that was probes plugin health score probes. Anything else you wanted to note there Chris. Yeah, maybe we should talk a bit about size of project this time or four projects are medium, which means that they wouldn't. They're not. They would finish by the end of summer. And they wouldn't be, well, unless we have some exceptions, I guess, then since they wouldn't go over it. Yeah, so as far as I understand it all of the projects are medium right plan to end by summer. Yep. So it was around September. And end of summer. On September again. Great. Thank you Chris thanks very much. So the next next topic topic was on community feedback suggestions so this was when we had discussed last week and I've not seen any further comments we had discussed it and I included the notes in in the comment here. About end users using the ratings and possibly consider accepting general text. Meg I know this is when we've involved you in the discussions quite deeply anything that you wanted to observe there. No, no. Okay. Great. So we, we continue with that one then the documentation transition from Java 11 to Java 17 is in progress now. So Kevin's working on various parts and pieces he's identified some places where that were that needed more than just a simple Oh, replace 11 with 17 like this page for instance, where we've got a page a section of paragraph that talks about running Jenkins on Java 11 and Docker, but we have no paragraph that guides them to how to run with Java 17 instructions are pretty easy. Oh dear. Oh yes, and it mentions it here. But what he's going to do is create a separate paragraph that is running with Java 17. Oops. So that that is the first thing that a user sees instead of reading how to run with Java 11. Okay. Good. Any, any questions on the Java 11 to Java 17 Oh, and, and I take it back I do have one more exciting piece of news June 2023 is the scheduled release of Debian 12. It was the catalyst for us to say let's remove. Let's shift our install instructions to Java 17 because this thing won't deliver Java 11. Okay. I got a question though. Yes. About this. Like, do we have like to switch over to 17 as well. I'm not really. I'm sorry. For what purpose do we have to switch over to Java 17 I missed one word in there Chris. Oh, the plugins. Oh no no actually they don't good question. So do plugins like some people might be asking. So your question is do plugins need to switch to require Java 17. Yep. Yeah. No, that's a really good question. The answer is no, but we strongly recommend that plugins test with both Java 11 and 17. Okay. And so in the tutorial in the improve a plugin tutorial we give them an example. So if we look up strong one if we look at the improve a plugin tutorial. We tell them when you add your Jenkins file. Test Java 11. In this case the example is test Java 11 on Windows test Java 17 on Linux so that both get tested and you know that your plugin supports compilation and running its tests with both Java 11 and Java 17. Did that answer your question Chris. Yep. And one of the things we've found there is that there are still some few plugins that don't support operation with Java 17 and need some additional improvements. So that one of the benefits of that step is the maintainer of the plugin will detect in their normal course of development. Oh, I've got a Java 17 problem I need to fix this. Yeah, me too. I do actually that's a plugin with some issues with 17 because I think it was like some, some class is being dedicated and no longer supported in 17 have to move it from one of the plugins and maintaining. Right. Yeah, yeah, good, good point. Absolutely. Okay. Anything else on Java 11 to Java 17 documentation transition. Yeah, is it is it an active PR like it's in a working on it. I don't think I don't think he's opened the first PR yet let's look and see. So it's like we're waiting if we look at Kevin's. Whoops if we look at his copy here. And let's go see if he's got an open PR right now I haven't, I haven't looked to see if he's got any open P oops, wrong one. This one. Okay, Martin's 27. No he doesn't have any open pull request yet for it he's been just been working through still on his local development environment. Okay, okay I see. Any other questions on the transition of documentation. Yes, I'm just wondering, it's like, it's any other documentation sections we need to update besides the one we discussed. There's a possibility that might be something we just just double check. Yeah, I think there are, there are quite a number of places that can be updated and Kevin's planning to, to touch each of them but was your, your thinking have somebody else help that or. So these are the, these are the items that he's identified. Okay. Yeah, I should be should be like everything looks like. Okay. Is there anything in the docs about agents. Agents and the Java version they use. Right, right. When I was there with there were people who were confused that you couldn't run any agents from a version of Java that had been deprecated until you know just to make sure there weren't any notes like that. And there, there are instructions in the documentation that say that the agent Java version must match the, the controller Java version. And that's part of this for instance the Java upgrade guidelines, where it says, hey you must have the correct JVM version on the agents, and it must match the JVM version on the controller. Okay. So that has changed then okay. See how out of it I am. Well, and this was one where this was was a lot there was a lot of noise about this during the Java eight to Java 11 transition is people said oh but I must have Java eight out on my agents. No, no you can't you have to have Java 11 on agents if you've got a Java 11 controller. Okay. So that's your question. Yes, yes, I was completely out of it so great. Okay. Any other topics on documentation transition from Java 11 to Java 17. Okay, so next topic is end of life notifications. We discussed this two or three meetings ago. There is now an open poll request. It's in draft state because we've realized thanks to good review from Tim Jacome. That the way it's structured right now isn't viable. It needs to be reworked. But the concept is good. Let's see if we can get that poll request and we'll show you what the screenshot looks like. Oops, it would help if I look at Jenkins core instead of the docs. Okay, so the UI will look like this. The example is for red hat for red head seven. A pop up or a subsection of the page that says, hey, your operating system will no longer be supported by Jenkins after such and such a date. And please plan your upgrade so that you're off of this thing before we end support of it. And then a link to documentation that gives more details. Nice. And now this piece is the piece that highlights that it needs to be redone because what I did was I created a monitor for each operating system version. Tim correctly noted. The controller runs only one operating system. So we could just iterate over all the choices find the one they are running and tell them about that one we don't need to have fedora 36 listed in this list. If they're not running fedora 36 and Basel Crow noted, he thinks really the piece of this that I was asking about early end of life. His answer was, look, end of life is already already happening. And has in many cases happened for this operating system version, because the system debased RPM installer no longer supports it. So, and then the, the container image is no longer maintained and hasn't been maintained for two and a half years. So people who are choosing to use that container image or using a badly outdated, undefended thing. And then it's got ancient versions of some very important utilities. And so his argument was, look, let's just declare it. There isn't any real discussion needed. Yeah. Good. Fast to the better right. Right. And that's this. The idea is this thing will appear to the user tell them your operating system is going to be end of life. So you need to get off of that thing soon. And that's, that's really all that I had for today any other topics. I might have a question to discuss. It's kind of something at the random. I saw if it goes to documentation. If you say like go to Jenkins style. So you want to go here. If you go to Jenkins style, if you go to documentation, if you go to the user's, I think it's developers got right. Okay. Yeah, that one. Yeah. So if you click on it, if it, if you like, if we can see a lot of the pages with like, yeah, we'll try and go with the warning, but then one icon. So click on any one of them. So, I'm just wondering is like, I have been contemplating like happening out contributing by contributing like by working through the light one by one. These items to like add contents to them. So do you think it's a good thing to do. It will be available to the community. I don't think so. I think it would be, well, at least for me, I think it would be very valuable. Some of them, it may be as simple as declaring this thing is actually already well enough described. So for instance, the internationalization section as I look at this one. I'm not sure that there's much more to say other than possibly we add a section about crowd in other than that. Okay, other than that it describes how do you internationalize Java. How do you do it in jelly. I'm not even sure we want to suggest to people use groovy for views anymore. And so this one I think is already in quite good, quite good condition, and maybe a link to or the crowd in localization video embedded and then we remove the work in progress indicator. Yes, that would be that would be deeply appreciated Chris. Okay, cool. So I will like I start. I think right around time we start some of code. Great. Thank you. Yeah. So reduce improving. Resolving or improving the developer documentation so that we can remove the work in progress flags. Right. And I think that's that's yeah that would be much appreciated. I may need to get involved for life for some discussion or what to do one not to add what to include because I don't have a very good sense about yet. And many your contribution. And I would be more than delighted to be involved. Okay, cool. So, and to highlight one that is of interest to me this testing one is one that I've been wanting to add to. And it's actually in quite quite a good bunch of contact content here. Some of the things yeah so I at least for our Google summer of code student for the get lab get lab plug in modernization. This testing page is quite useful already showing them hey here's how you can use the Jenkins test harness and here's how you can use do pipeline tests and here's how you can test. Now what it doesn't have here is config oh no. Yeah it does not have configuration as code test but it does have configuration round trip so some of the some of the really cool kind of testing techniques that are in Jenkins already are described here and so and I think for our GSoc students it may help our GSoc participants. Or we can work with the GSoc students at content while we're going to together. All right, any other topics for today's discussion. Nope. Nope. Okay. Thanks everybody I'm going to call us to an end today I'm a little weary. And so we're going to call it a good one. I'll. If you don't see me next week it's because I was visiting CD con in Vancouver Canada. I'll be there Monday and Tuesday back in the office Wednesday and we'll we'll see how things go from there. Okay, cool. Thanks everybody. Good week everybody.