 Welcome everyone. It's the 24th of June. This is documentation office hours. Items I've got on the agenda. Action items. Google summer of code pipeline steps doc generator. Longstanding poll requests. We don't need to talk about change log and upgrade guide because that's been delivered. I guess maybe we should put in a news item here, which is Jenkins 2.346.1 release. Then require Java 11 that's coming and support Java 17 migration of user stories nothing to talk about there and then open action items for me on upcoming blog posts. What other topics need to be on the agenda. Yes, so from my side. There's one ticket which is open for a UI improvement. So I want to discuss more on that I am searching for it. I'll provide the link as well in few minutes. Okay. Oh, is this is a this is a documentation UI or a Jenkins UI. Jenkins UI. Okay. All right. Well, good. So dear us. Let's, let's have you will put that right at the top of the list. Make sure that we get that topic covered. Good. Anything Meg from you. Yep. All right. So how about let's start on the action items for now while deraches is checking on the other topic. I've still got the action to archive the documentation mailing list and use community at Jenkins.io. We've got an action item to create three blog posts, CD con award winners Jenkins contributor summit summary from CD con and she code Africa contribute on results by way of news Jenkins 2.346.1 has released. This is a security release. It includes it also had a matching Jenkins 2.332.4 and Jenkins 2.356. So D Raj, has you found that you I improvement ticket. Yes. Okay, and what is it. Oh, good. I shared it in the chat. Got it. Okay. There's a rendering problem. And I reported it. Then I tried to look for a solution long time back when I reported, then I could not find it then I forgot about this. Then someone very kind enough person posted a comment feud. I think last week that hey, this is what he should be doing something like that. And I think that would work. And then I tried to think about like, how would I do it because this shows up on a particular Jenkins version. And in my local installation of Jenkins, it shows up the latest one so So what would be the action items from now on should it be like, I should use a particular version of Jenkins as I have noted down in this ticket. So, so usually the way you did it here is is a good a good point and you noted hey it's version job filters. So, so your concern is, is that the right way to log the bug. Yes, and also, how would I use a particular version of Jenkins, because mine is latest by default. Oh, well, so all you have to do is report which version you were using. So by your saying hey I was using Jenkins 2.277.3. Now, if you want to use an arbitrary Jenkins version the easiest way to do that is like this you say Docker run, and then Jenkins slash Jenkins colon and let's say you want to use 2.346.1. That's how you do it. Now, this particular computer's already got a Docker image running at that location so let me switch to another computer will do it here. So when I do that, it's going to open up for 8080 on this computer running Jenkins 2.346.1 so I remember that password and I go to that Jenkins controller here I have a one here that's convenient and it will. It's starting Jenkins and it'll ask me soon to insert that password. So, did that answer your question on how to run a specific Jenkins version. Yes, it did. So the magic for me is this Docker run command that lets me choose arbitrary Jenkins versions pretty easily. Now if you if there's something that that doesn't make sense to you where you say oh hey that's not the hopes no apparently I entered the wrong password let's get the correct password. Much better. Okay and I'm going to select no plugins to install. And there we are. And when I click save and continue it's ready to go. And now I have a Jenkins running with exactly that version and usually it would have no plugins installed. Good. Yes, and it crop up shows the correct warning. So did now in terms of this specific bug report. If you'd like we could do a quick check right now I think I use exactly this configuration myself for the current version of Jenkins. I'm going to check you want to show we do a look to see if the current version looks the same. Yes, please. Okay, so. All right, so let's look here at Jenkins home and we're going to use this one. So the plugin that's being used is view job filter and I actually have views already defined. Let's borrow this one. The defined named failed. And this failed view says here let's go with unstable it's easier. There we go so this one. Now if I edit the view it should show me. Here is the job statuses filter is and is was that the thing you were using no you were using build statuses filter so maybe I do need to go back. I do need to go back to fail because that's build statuses filter. No, that's still job status. Whoops. I think you can click on add job filter below drop down and okay manually. Okay, so add filter build statuses. Yes, so 123. The checkbox you can see it is before the build statuses. Yes, right. So currently building and the same thing here right current here's here's the checkbox that's probably associated with currently building right. And this one is associated with never built and this one is associated with in build queue. So yeah so the problem is still very much there as far as I can tell. You don't see it in 2.277.1, but this shows it in 319.1. And in. Yeah, so. So it definitely as far as I can tell it is still a problem. Okay, so I can say you're saying I can work on it and the latest Jenkins version as well. Yes. Yeah, so as far as I can tell, I could I could check on a weekly version that's absolutely the latest this is latest Jenkins LTS but I have no reason to think that it's not a problem there as well. So let me capture a screenshot just to say that we've, oops, well that'll be fine. We've got a screenshot captured will edit it, crop it. Okay, so the thing we need to do is job statuses filter build statuses filter. Right, and then. Now what we need is we need an arrow that points to whoops this. Sorry, my editing capabilities are a little bit imperfect right now. And we need a very useful tool. Oh, I love this particular tool. It is absolutely a wonderful way to do image editing. And then text. Okay, so, and what would we say here's something like checkbox is left of job statuses, but should be left of stable like that. There we go. And I'll update that confirmed still an issue with latest release of view filter plug in and Jenkins 2.346.1 and we drag this here put it there. And if I got it right when we do the visual we'll see it. There it is. So it's a little bit big as an image goes but I assume that's workable. You're okay if I add that comment. Yes. Okay, great. So that was this ticket. Let's put it there. Checkbox alignment. Miss aligned misalignment in filter plugin. Alright, anything else on that topic. Not really because in the person pointed out the kind of edits that I need to do. I'll try to find the file where that is supposed to go and propose the changes. Alright, thank you. Thanks very much. Thanks a lot. So, a question on that. And I don't expect the exact answer but what's the best way to find the file where I need to do the change should I search for the text job statuses on the whole code base or how do you go about this. Yeah, so that's so I would, I think since this has been reported against the view job filters plug in, I would open the view job filters plug in. So view job view job. View job filters. And on GitHub search for slash and what was it it was viewed. No, it was build statuses filter. So again slash build statuses filter. Let's see if we can find it this way. It looks promising. Here's a jelly style. Build statuses. I don't see one yeah so let's let's do some more looking so if I back to the picture we took currently building. There we go. Yeah so this I'm reasonably sure this is the place you want to be. Here's build statuses currently building never built in build. So now your initial report. Hey, they are correct in 2.277.4.1 or is that that's where you know that's correct. I get it. Okay, so do you know maybe maybe what what you need to know is the secret command line option that will let you see the problem with the exact sequence you were trying to run. So you did a maven HPI colon right. Yes. So if you do something very similar. And I'll just put it right in this comment. You could be able to see that from a debugger or a development environment with maven clean Jenkins dot version equals two dot four six dot one. And what that will do is run run run maven and use Jenkins current version, rather than the version that the plugin declares as its minimum version. Maybe it's so cool. Yeah it's interesting isn't it it's it's a lot of people use it to do a lot of interesting things. Did that did that help. Yes, it definitely did. I know how to install that particular Jenkins and I know where to look. And I know the changes that I need to do. Thanks to the person posted the screenshot I think I'll be able to move forward with this. Great. Excellent. Thank you. Thanks for being willing to work on that. Thank you. All right, next topic then was Google summer of code and the pipeline steps doc generator. The here we had a full request submitted to Jenkins.io from VHAN, and that whole request. What did why did that not tell us VHAN pull request was submitted and it's been merged. So if we look here at the whole request you'll see this independent scrolling the documentation sidebar. Then there are two pull requests to the pipeline steps doc generator. And these need review they were submitted within the last day or so. I reviewed one of them just briefly and had a surprise and I've given a comment. I assume none of you have questions on this one. Any any concerns or topics. Nothing really, but I saw the preview mode of this PR and it was very neat. Like on the left side, nothing is getting scrolled and on the right side you have to scroll it. That was very neat. Right. Well, and the dismaying part for me there is I'm, I know it's been merged. It was merged eight hours ago. And yet when I look at it now on Jenkins.io, it still has the old scrolling behavior. And with the old scrolling behavior, it's, it's, I'm not sure if it's a caching problem what's going on but if we look here the one that where I was seeing was managing Jenkins and if I pick a long page like features controlled with system properties. I expected this to stick, but it doesn't stick now. And I'm not sure why. In his PR he did mention a page where it was visible. Okay, well, let's, so let's see, maybe that'll be me the hint for me. So, yeah, see the example here was configuration. Oh, no, that's, that's a different example. That's his example of somebody else using the same technique. Just a moment. Okay, this one so was on securing Jenkins. So if I navigate to securing Jenkins. I, when I scroll up and down, it does not stick and I'm not sure if that's intentional or more accidental. And so I think needs more discussion or something's wrong and I'm not not refreshing cash well enough, I don't know. So PR got merged. Yes, feature and it's not visible on the website. That's what I'm seeing anyway it does. Well, and I haven't looked inside the JavaScript code from the website to see if it is. If the changes are actually there and they're just they've somehow been changed in a way that they are no longer having the effect so if I look at what files are changed. I should be able to look what should we be able to see the Jenkins that CSS file should should be findable somehow to confirm that these changes were made. The comment says making the site bars crawl independently. So it is intended to work that way. I think so. Right, I think you're right. Okay. So I think we might be to tell the Han about this. In fact, maybe what I'll do is I'll just make a comment here and mention fixed table of content the unmoving table of contents, it behaving as you is. Let's get the example page is this page behaving as you expect that you moved is this as well. Oh, oops. Thank you. Let's make sure that I write English text. There we go. Okay. So that that's it that I've got on Google summer of code pipeline step stock generator. Any other concerns or questions. No, nothing more. That's all. Okay. Okay, then we had another topic was our long standing pull requests, the adopt a plugin pull request and make security re were documents security docs rework. And I apologize, neither of those have had progress. Meg, I'm really sorry. And Meg, you, you may need to unmute yourself. Next topic was on Java 11. And that's next Tuesday when we've got it. Huh. Yeah, no, that's. So, is there anything there or. No, I've made no progress. Sorry, but nothing to report. I don't think with the security release this week. I mean, the blockers Daniel so. Yeah. All right. Java 11 we've got a blog post coming and next Tuesday a release that will be the first Jenkins version that mandates you must run at least Java 11. Yeah, yeah. And we've announced full support for Java 17. So, if you're running either Java, if you're running Java eight, you need to switch. And if you're not running Java 17 yet it's worth experimenting. And that's that's those are all the topics I had any other topics. Okay, we've done a past exercise trying to look for outdated PRs that we could close. Recently, my focus has been trying to get PRs emerge that are in the queue we've got several screenshot updates that need review and it's just a matter of reviewing and getting them in. So we're up to 30 open pull requests again my goal is to get it back down to 25. 25 ones so that's nice. They are exactly these are new ones and we'll try to get them resolved and merged in. All right, anything else for today. No, we need to go into those old PRs. We could we could do it tonight if you'd like or we could do it today. I have to remember it's not night everywhere. We could do it today and look at those PRs we could do it whenever. I'm going to be leaving you soon. Okay, so whatever works for you. Yeah, I think for me dear I should maybe best if I, if we hold off on today, let Meg disconnect and and I'll make some progress on later I've got those three blog posts I've got to do I've got other things that have got to take higher priority. Hmm, makes sense. No problem at all. All right. Actually, let's I take it back. Let's take this one. Because we've got some requests for. Yeah, this one just needed. Okay, oh, like I said, he thought this was ready for review so this one needs more discussion because yeah there's, there's a whole bunch of conversation in the bug report about this thing. All right, I'm going to go ahead and call us done for today. Thanks everybody. Have a good week. Thank you. Bye.