Jenkins UX SIG Meeting 19 Aug 2026

Welcome everyone. This is the Jenkins user experience special interest group meeting. It's the 19th of August 2026. Um, key topic for me, the first topic on my list was the side panel pull request that was merged in 2.577 has caused a number of bug reports. And the the regressions are serious enough that the plan right now is to revert it. Um, I intend to revert it within the next say 24 hours. It's passed my interactive test. The revert has passed my interactive testing. It's passed all sorts of other automated checks including plugin bomb. So, I think and we haven't seen enough motion in my mind at least from Jan to immediately fix the problems that have been reported. So, to see a hint of the kinds of problems, these all these that are listed as regression here are from that pull request. So, 1 2 3 4 5 and for me that's we need time to revisit it to resolve those concerns and keep users of Jenkins weekly okay. Any any comments, concerns, or objections from those of you on the call? >> Not any objections, but what are these problems with other plugins or are these Jenkins core problems? >> These are Jenkins core problems actually. So, automatic console logging is specifically Jenkins core, scroll all page reasons Jenkins core, uh double scroll bars. Now, this one is a plugin issue, but it's a very widely used plugin and so the hunch is we've got to fix it. It was also detected by CloudBees in their use. So, it's there are two things, customizable header and whatever CloudBees is doing with it. >> Okay. >> So, for me, it it's it's not any any black mark on It's not any any deprecation or root denigration of Jan's work. It's just there were a a number of unexpected surprises there that and needs a chance to be reworked. >> Yeah. >> So, the revert Oh, go ahead. >> Yeah, I think we can give it some more time when we have it in development. >> Exactly. >> locally and see it. It's fine. >> Well, and and August is really a safe month for us to revert things. Truthfully, August is pretty light in terms of European vacations. So, why not? >> Yeah. >> Uh um the reverting pull request has more details on it. Next topic for me though was what I think is really exciting. We now have a unit test framework for JavaScript in Jenkins core, V test. And and this came We've got a a It's in the pull request and it's apparently a very a relatively popular framework. There's a getting started page from the project that looks looks very nice. It looks like this is a really well thought project. And there are a number of YouTube videos that provide tutorials. So, my question was we've got a bunch of new contributors who are interested in contributing. Can we point them to writing JavaScript tests? I guess Uli, this is a question I'd like to ask to you with your JavaScript experience. Is JavaScript testing something that a new contributor could auto test automation something a new contributor could reasonably do. >> I think this is a really good topic for newcomers because now with the help of yeah, AI, some new tests can be generated kind of quickly and it would help to yeah, improve our quality of JavaScript sources. So, even in my plugins, I don't have a JavaScript tests because yeah, JavaScript is so small and it would be really helpful if we have some yeah, automatic framework that checks these elements as well. >> And and the the interesting or the exciting thing for me about this is it automatically includes the test results into the reports page on ci.jenkins.io. So, we get the results. Now, Arav Singh I see just joined us and Arav, I believe you've been doing some JavaScript work recently. Do you have experience with V test and do you want to share any of that experience with us? Sorry Arav, I'm having difficulty hearing you. You may need to change your microphone. Okay, we can't hear you. Maybe you could share your thoughts in the chat, Arav. Arav had had done several pull requests relative to to UI improvements and so I think is a credible new contributor that we can use to to consider is this a good fit. On the experimental UI, so next topic, given that this is mostly around Yiannis, I'm prone to just leave this other than unless there are leave this without spending a lot of time on it unless there are things that Uli, you, or Chris want to be sure we discuss in this context. >> I think it for me it's fine to skip because >> [clears throat] >> I recently had no time to improve my plugins in the last couple of months. But yeah, I think in September I will start when there is some some free time and yeah, so I think we can wait for the next meeting. >> Great. Yeah, so oh go ahead, Chris. >> Yeah, just one thing I want to bring up like when we like for the default pods, are we postponing it until like later, I think? >> We are. So it one of the constraints was it didn't make it it didn't make it into a weekly release as the default prior to our selection of the new LTS baseline. Therefore, it won't be in the next LTS cycle. So 2.576.1 two and three will release in September, October, and November. So the next opportunity for this in LTS will be December of 2026. >> Okay. >> Now it is I liked your Chris had sent a an invitation to others saying, "Hey, start testing this. Spend more time in it." And I've been switching my managed Jenkins use to use the new UI trying to drive that. And I've found I have several things I need to fix in my plugins to be sure that they fit well. >> Nice. >> So so it's good. People should switch it on. It's been there long enough. It's mature enough that bugs that we're finding should be interesting. This and for example, I looked at these. There are certainly still major work that's needed in the role strategy plug-in. Um these pull requests from Tim Jacomb are there waiting for review, some of them, others just in draft. He's done major rework of the UI in the role strategy plug-in. So it's it's a much different UI now thanks to his work. But they'll need to be reviewed uh and tested, etc. Okay, so I'm going to continue on to our next section that's that's web UI work on Jenkins core. And right now we have 48 open pull requests. Three that three three that are are merged in the last month, but the others are for me in progress in various stages. Marcus Winter, his work, he's continued his work on the new UI for agents. And he just recently made changes there. We have some from new contributors that are proceeding. And they're going slowly, but proceeding. And a few, two of them with unresolved merge conflicts that I'm prone to say, "Hey, if you don't resolve these conflicts, we're going to close them." Because it usually if a merge conflict exists, it usually means that the submitter has abandoned the pull request. And likewise for some of these olders that have changes requested. Any comments, Uli, in terms of this web UI work? Or Chris, any worries you have about that approach? >> No not for me. >> Not for me either. >> Great. All right. And those were the topics I had. Now, Arav, I see that you've joined us again. Arav, were there specific topics you wanted to wanted to discuss? >> No, actually I've been contributing into Jenkins currently lately. So, actually I just wanted to know what is going on in the meeting so that I can connect better and then, you know, have a good understanding about the community. >> Great. Well, we're we're delighted that you're here. Thanks very much for your contributions. I wanted to take a look. I believe you are this user. Is that correct? Oh, no, no, no. Nope, that's [clears throat] wrong. I got the wrong user. >> user. >> Okay. I If I look like this, there we go. >> one, the first one, yeah. >> Excellent. All right, so we've got these these that you had submitted. Good. All right. Well, thanks for your contributions and we look forward to you continuing. >> Yeah, thank you so much. >> Any other topics we need to be sure we discuss today? >> Nope. >> All right. Thanks, everyone. Recording will be available in 24 to 48 hours. And