 So next topic, I guess that's what I could put that's what's the current status with MS always sponsorship Basically, we are back to the previous situation where club is paying the accounts. So the Amazon budget we got is totally spent by now and So far we won't have more budget from Amazon Did Amazon confirm that or is it just the current status of affairs? Last time I was in contact with them that was Yeah, we It's difficult to know for sure if they won't sponsor us anymore, but at least Any other topic Um on the security release for tomorrow, are there any things that we need to be aware of for as infra? So we've got a weekly that will be out tomorrow We've got the lts 2.277.2 that will be out tomorrow No, um I think we are on track for the release We shouldn't have I'm not expecting anything tomorrow But As long as we don't play with the release instance Well, and I assume the the release is already built The yes Daniel has already certainly built it and has it ready and staged privately So that it's not not that we're dependent on the release infrastructure tomorrow We're dependent on delivery infrastructure tomorrow And and the mirrors etc. So so far we don't stage the packaging So so far we we still have to package that process usually take 15 minutes. So we still rely on the release environments um But um, indeed the Jenkins core version is already built and staged So we just have to promote which is something that Daniel does manually at the end of the operation Okay, so the war file is built and ready to package packaging will actually happen tomorrow. Yes Okay, got it. Thank you So any last minute topic? Yeah, I had a question. So let's assume we need to build another lts baseline for 2.263 How long would approximately take after we have a branch ready three to four hours, right so Oh, I mean, who are you targeting team or me? Yes, so I'm still a bit concerned about tables to diffs impact And because with the tomorrow's release, we might be pushing the user stop date We know about the number of plugins which are still more compatible So I wonder what would be our escape hatch if There is a major negative feedback in the community after the release so basically the Once once you have the codes on the on the branch on Jenkins CI slash Jenkins once your branch is ready Um, the release environment it takes approximately two hours to build Jenkins the war file But basically yes, and we clear the same Yes, so in terms of in terms of build time, it's exactly the same in terms of configuration Um, the lts require a little bit more work, but it's like maybe 10 minutes 10 15 minutes It's just a time to to update the file with the correct configuration And someone to review that configuration um, so yeah, it is Approximately approximately take one hour 32 hours to build the Jenkins core and then 15 minutes to the package and publish that those new packages Okay I would be more concerned isn't the bigger challenge that we've got to have whatever fixes are implemented in 2.277.2 would have to be back ported and verified on the 2.263 base And I was worried that that would I think that would take more time than the than the time to do the the build But are all like are you assuming that Daniel or others would already have done that Even before before making a public before making 277.2 publicly available Yeah, it's something to be done if we decide to do so Okay, got it. It's that's still a to be done. Got it. Thank you Well, it's not to be done because there is no confirmation that it needs to be done I was just wondering if there is a strong pressure to do that How long could it take? Got it. Okay. Thanks I still have a few plugins to fix for tonight including scripture Do you have an idea how long it would take to back port everything? I don't know what changes were I I don't know what changes were in 277.2 And so I'm intentionally staying staying away from that trusting the security team to do it and But I just I'm not that big There are some potential downsides like In the GTA version differences, etc But yeah, I wouldn't expect it to be a major deal Maybe Kim has more insights No, there's not too serious from what I've just begun on the look at Okay But then then I'll probably wait a little bit before we start in the real environments So we just keep it available if we have to read something Great, right. Any other question suggestion? Then I propose to finish the meeting here. Thanks for your time And see you on RC. Have a good day. Bye. Bye. Thanks Everybody welcome for this new Jenkins infrastructure meeting. Um So Before so few announcements before we continue the first one is we are going to upgrade the community's cluster Used by the Jenkins project next week We are planning to do that on Thursday on Tuesday. Sorry. Sorry next Tuesday Um, I'll do that with carrots in Damien. So normally normally everything I mean, we shouldn't have interruption But yeah, better to prepare I don't start in advance. Anyway Um, the second topic that I pretty want to mention is I created the key tap. I don't need group and So the rule is as a contributor once you have privileged access If you know that you won't be able to contribute In a short in short term It's just better to to ask to be to have your permission reduced. So we don't take the risk Um, I'm getting compromise for whatever the reason so um That was the second thing that I want to mention Um, so if we go back to the ongoing work, um this morning we we did uh specific Releases using release.ci and we faced um a bunch of issues. Um for some reason So basically we got time out issues between the Jenkins agents and the Jenkins controller. Um So we were affected by the same behavior on infrared ci last week A daemon made a suggestions to switch The connection using web circuits. Um, which seems to be solving the connection issues I still don't understand why we were affected now while while we are affected now By not using the web circuits um But yeah switching to the web second made made it working Maybe I'll let you have some ideas there No, not right away I need to take a look because I haven't seen the problem I'm just wondering if if today's is the way to go using web circuits by default So current state of web circuits that it's officially still in preview because Web circuits works perfectly fine on java 8 for java 11 and hence for our instances There are some unknown issues with certificate Which haven't been troubleshooted yet. So We reviewed it with jc agreec and jc said that most likely it's a specific environment issue But we have never really tested that so Basically if you use web sockets with java 11 formally you're still using unsupported configuration Okay So then then then I can share with you the the message like at this morning The second question is that we definitely need to get it over the line Is just a matter of who would be contributing to it because jc is is quite other projects at the moment Oh, like when you when you say java 11 Is that on the controller side or the agent side or Well As a project we officially do not recommend running different versions of java on controllers and Agents because it may lead to various Interesting situations in terms of serialization of base types provided by gdk Well, not base types just classes by gdk because they may have a different binary format so We do not really test combinations of java 11 controller with java 8 agents or otherwise And personally I wouldn't recommend this configuration Yeah, just for a content so i'm pretty sure we are not using java 8 Yes, so caging is that you and all modern instances run with java 11 If you want to build with java 8 you basically set up environment. So you build runs with java 8 But at the same time Yes, the instance should be using java 11. I guess Well, maybe it's not the case for docker images At least in the Jenkins infra project release the ti and for the ti and ci the Jenkins that are you are running on java even trust it at ci And serve the ti are running in java 8 Yeah, and things like the agents some of those agents will be running java 8. They're like the aci agents or We'll be running java 8. They won't be running java 11 with a separate java for the build Yeah But it was noting that our instances are relatively simple when you take the number of installed plugins So there are some foundation ones And there is no guarantee that Any plugin would work on such configuration There's a former remote in 20. I do recommend that but yeah, it works It's going to be even more fun with java 17 But I guess we can discuss it Closer to the autumn Thanks. Any other suggestion regarding the issue we had this morning So basically we have we have prs to change the configuration of infra.ci We just did the manual change this morning so we could move faster But once the release is over, we'll We'll apply the configuration change So that's that thing. That's anything so until tomorrow We put on older java infra that ci that managed taking this cluster. So no change right now to that The next topic So if you have some the thing that you want to bring That's a great break time as we don't have a lot of things So something that I want to share is some experimentation that I did with key cloak last week So key cloak offered the possibility to delete to allow users to delete their own accounts I just faced To main I mean once minor issue key cloak changed the team So we want if you want to keep using the Jenkins team We have to do some minor modification, which is not a big deal But yes, but more importantly deleting users only delete the users from key cloak not from LDAP Which means that If you really want to use that feature, we really have to switch using key cloak Instead of that for issues touching the radio That's the one thing and the second limitation is deleting user to not delete the group inside Key cloak, which means that in the current states the next time a user create a new account with