 Welcome. It's the 8th of September 2023. This is Jenkins documentation office hours. Topics I've got on the list for today. Google summer of code. Plug in bill of materials version selection, Java and Jenkins. And existing requirements support policy and DevOps world tour. This one's actually done in terms of a blog post anything else Chris that you want to add to the list. Nope. Okay. All right. Well, so then let's look at dog at Google summer of code first. So Docker compose as far as I can tell. This will need to this will be. It's complete. As a project needs more work to do. And include in the documentation because we need container images. Yep. And a report containers and a repository to host those containers. And jobs to maintain them. Right Jenkins jobs to maintain them. And those need the infra team and we can hope during Hacktoberfest. I don't think we're going to get them in September because we've got so many other things in for in for is doing. The vision documentation this one is still in progress right still developing. Yep. So we simplify the twin for the block. So to use just check gas be Okay, say that again. So, before we're considering using a strappy back end for all right. But we've given with abandon that fine. So we now we're just going to use gas be. And good. Okay. Yeah, and get up for review. Very good. Okay. So I'm just going to say it that way use gas using gas be as the front end and get up for review. Good. Okay. Anything else that I had seen a pull request coming through pull requests are still arriving. Yep. I saw one with the blog post layout. Yeah, this morning. So we do it. I added it. I had the commits to it to update the columns further further layout. And I think we are on track to complete and who reads. Very good. Any other things that you want to highlight or should is it something you want to we would like to show us we want to show it on screen or anything like that. No, because we're we're still developing it. Okay. All right. Good. All right. Anything else on version documentation. I'm also didn't toys. I on it was I like, I think, I think from what they told me, I didn't check he said he has like fixed most of the book and things. Also for for for the drop down menu above. I can check now if you still like that. That's great. And I'm happy to happy to check we can do a test drive. Is it available on a on a site that we could go look at it from here and if not I'm okay if we if we say no we're not going to do it. It's the same link we we have before. So if you stick it in a document somewhere so you should be right so now I just need to scroll a little bit and let's go find it. Oh, it's in my it's in an archive. Hang on. I think we have to go back one. Okay. demo site. There it is. Okay, good. We'll just put that right into the page that we've currently got. Okay. Okay. And so some examples of first things first let's switch to a. I remember right. Previously he had versioning. Yes, there we go for a 2.401.3. Okay, so here we see version and now in terms of broken links. Do you have a recollection where they were there's certainly plenty of links this one. There was some booking links before so most of the menu menu items are broken top navigation so. So this one for instance. Working. Okay, still working. Okay, I need to push a little bit more. Because he told me that they're fixed. Well, and maybe they're fixed and just not deployed to the to the GitHub, the GitHub pages site. Yeah, maybe. Because from what he told me is like except for a few pages that has that I have not been developed yet. Maybe it's these that I don't know. Yeah, maybe maybe they're not done yet because they're part of the website. But the navigation so the things that were broken were from the top level here not from inside the pages. The in page navigation links seem to work just fine. Yeah, some like some of links were broken before. Left hand side. But they should be working now. Yeah, so and in in page navigation so the the chapter to chapter navigation seems to be working. Yeah, I think it's okay. Okay, so that's an internal one that's not working. All right, so. All right, because that was a link to the security pages which are over here and securities a different thing right. That one is not a version site at all that'd be a Gatsby thing. Nice. I find the layout very pleasant. This is this is looking really really good. Yeah. And it feels quite responsive coming from GitHub pages so I don't don't feel like there's any any. There's certainly no content generation when I'm when I'm viewing the page right these are just static pages. Yeah. Well, we may we may still need to fix the defense page because like the the event item. So that would be a maybe lower left hand corner. So, so which one this one events events. Ah, here we go this one. I mean it's done yet the major events. So we have to work on the calendar. So this one. Got it. But but the Google calendar is embedded as expected. Okay. Yeah. Yeah, so this card based layout isn't there yet. Hmm. That things like that for now is high coded the data, but we have to fetch us somehow from the database or from the like. Okay. Yeah. And it looks like the books layout looks quite good. Nice. Yeah. Okay this one. So should we we do it should we do it so it's like it as follows what we have right now because I I'm not sure we should do it this way. See I like I like the layout of the current page better for that one personally now. I'm I'm opened other people's feedback but for me this one. I find more readable. I think so too. Yeah. Then the house can to reverse the change. Now is the artwork page. Okay, so the artwork pages and isn't working yet either. No. Infection. This this looks like great progress though Chris really impressive. See about artwork. Yeah, and that's. Let's do it this way. Okay. Not yet. So that that artwork is definitely not there yet. Yeah, so I have to ask you. Great. Yeah. This is the one he was working on. And so is it is it under the same locations they'll know. I think we're going to move it to the block. So like he can just direct it to block. Like Jenkins style maybe. Okay. Very good. And success stories still should navigate there. And that one. Yeah, we're 404. Okay. So we're going to move it to the spot where it's here. No. Okay. There we are. Nice. Anything else you'd like to highlight here. I think we still need to. To work on like perfecting it. So it takes the thing is I'm kind of worried about like we may take. A bit longer. Oh, I am. I am confident we will because we certainly can't. Right. Without having the top menus working without security there, et cetera. I mean, we've got, we, there are lots of more things to do, but this is really amazing progress in terms of what we see. Right. I mean, the navigation is so much better than this. Right. I don't, Vandy did a great job on this navigation as well, but I find this much more pleasant. Yeah, me too. And it's not introducing. Okay. So on the large ones, it does give us a scroll bar. And we get. The version choices. Nice. Yep. Very good. Anything else that we should show there. Nope. Okay. Good. All right. Then the next one was get lab plugin modernization. I still need to need to do the testing. Next week I'm at DevOps world. So there's a risk that I won't get to it until the following week. Let's make a note here of that meeting canceled for next week. DevOps world tour. In New York. Great. Yep. Anything else on Google summer of code. Oh, final presentation September 14, right? Yeah. Next Thursday. Great. Okay. How about a plugin have school project? Should we talk a bit about it? Sure. Yeah. Let's, we can. So are there things that you'd like to highlight there? So we got two blog posts. Pios. So. And one was merged, even though like some updates, it's necessary because like, we got some reviews after it was merged. Okay. So the merged pull request. Does it need changes based on the feedback? Yep. Because the feedback camera bit late. Okay. Great. All right. Yep. Anything else you want to highlight there? Not much. It seems like they are doing all right. So. Because like agents just came back to the holidays. Yeah. Good. Yep. Yep. Anything else? Nope. Okay. So choosing a plugin bill of materials version. I don't have any progress from last week and a none expected. For two to four weeks. Due to other priorities, right? I'd rather test the get lab plugin first and other things are higher priority than that. Okay. Now I've got this topic here that if you're willing to go through it with me, I'd love to, to bring up a, a diagram with you and talk about the diagram. Are you okay if we spend some time on Java support? Yeah. Sure. Okay. So here's this diagram that I've created. Trying to help me visualize. Java support in Jenkins. Yep. So let's go bigger on this so that it's more readable. So the, the concept here is that. We want to get to a model where we do. Two years, so Java releases are now coming out every two years. And they have a support lifespan of six years. So the proposal I'm, I'm suggesting here, and I'll be discussing it with the Jenkins board, Jenkins officers, and then with the developers list and the developers list. So what we want to do is that we switch, we work towards a model of two plus two plus two. Where the first two is two years of. Two years of support. The Java version, but not make it the minimum Java version required. So let's see, I need to change this wording. Daniel Beck suggested different wording. All right, right. Java 11 or newer. Or let's do it this way. Java 17 required. Okay. And this one is Java 17 or Java 21. Required. And this one is. Java 21 or Java 25. Required. And this one is Java 25 or Java 29 required. So do you see the pattern there? It's two years supported, but not required, not mandatory. Then two years when it becomes the mandatory version. And 233 required. There we go. And then two years where it's not supported. So the last two years of a Java versions life. We would have dropped support like we did with Java eight. Even before it reached end of end of support for Java itself. Because we don't want to carry the burden of always supporting three Java versions. There will be transition periods on these edges where we will probably support three Java versions for a period. But in general. Keep it simple with. A primary Java version and its next version getting ready and rotate that every two years. Does now the idea then is. One year before we make it required. We announced with an administrative monitor that, hey. We're going to make it required. Okay. Makes sense. Does. And now the other complexity here is we've got to do a transition period. So right now we're in. September of 2023, right? Where here we are in this six month window. And. In that six month window. We will in October. Turn switch on the administrative monitor warning about the end of life of Java 11. Then the proposal is we will in one year from then. In October of 2024. We will switch over and require up 17. And support Java 21. Okay. And then now the 17 life span. We will limit to one year. Rather than two years so that we can make the transition. Towards this two to two model. So with Java 17, it'll only be required for 12 months. Java 21, it'll be required for 18 months. And then when we finally get to 25, whoops. 25, it will be required for 24 months. Okay. Makes sense. And now we're on cadence 24 months, 24 months, et cetera. Any, any concerns or worries about, hey, that idea. Yeah, I'm, I'm just kind of concerned about like a four Java 17 and Java 21. Like the blue period, the job requires a bit of short on that. That's okay. And I agree this one, this one, one of the things that had been suggested by who Lee Hoffner was he suggested. Why, why don't we just skip Java 17 and jump right to Java 21. The answer is, I need to have this Java 17 transition period because enterprise customers need to transition through Java 17, particularly with enterprise customers of my employer cloud bees. So because we contribute a bunch of developers, I need that help. Okay. I think, I think we should keep Java 17 too. Good. All right. Any other, any other comments or concerns? No, just, just that, that was my concern. Great. Okay. All right. Well, that one, and I'll be bringing the topic to others for further discussion to see, okay, what, what, what other concerns are there about this idea? That's all that I had for today. Anything else from you, Chris? Not much. Okay. Then I'd propose, let's call it done. I've got some diagnosis I need to do. I'll show you the diagnosis problem. I've got to start diagnosing. But it doesn't need to be done during our time here. James Norard opened a help desk request. Back at the end of June. And he re, he opened a new one saying the same thing. But hey, this, the extensions index here. Is missing many, many extension points. And it's, it's, this is Jenkins core and Jenkins plugins providing these extension points. And the problem is tied to this tool. The back end extension indexer. Whose CI job is currently broken. Oh, okay. And not only is it CI job broken, but it's there's something even before the job was broken. That was not generating correctly. So, so there's research that needs to be done here to understand when did this break? Why did it break? What do we need to do to fix it? We had a similar problem with the pipeline steps doc generator and ended up writing some tests that found the problem and safeguarded us until we could fix it. Okay. I remember that one. Right. Exactly. And, and actually that was one that I think Vandit helped us with. No, no, no, it wasn't Vandit. It was last year's GSOC student that helped us with it. Right. Right. It was V Hanthora. Thank you. Yes. Yeah. All right. So any other topics for today? Nope. Okay. Let's call ourselves done then. Thanks very much. Okay. Thank you.