 Hello and welcome to the Jenkins infrastructure team meeting. We are the 14th of February with Mark White, Stefan Mel, Kevin Martens and I. As an announcement, the weekly is in progress. I think it's good. You'll check that just after this meeting, I think. We checked prior and everything is good except for the container images, all other parts and pieces. Oh, and we've got to check that the the change log has been published to the official location it's approved. I don't know if it's yet or yet actually arrived. Another announcement. There will be a plugin advisory tomorrow. That's right. That's right. Again, security. Tomorrow. I'll take the screen so I can more easily. Let's see in your preferences if I hide this one. Let's see where is how to okay where is oh there is this is the one that way we can see full width is that what you want it. If I can take the screen share so I can. You bet. Which screen are you seeing. Okay, perfect. So next week will be next week's and next yes, I don't remember. March 8 2.387.1. I'll put that in the notes. We. And I don't think there are upcoming calendar events. We can switch to the don't issue. The first one is one user who used his email instead of his username to login so no issue. It's forever. See 500 error he's got when using his email is the normal behavior of the application I think. It's perfect one that's around one missing documentation and current plugin page. It was an error. I've merged. See the car builder image. Innovate another but merge the car image. The car image. Which wasn't working for a plugin site. So I reverted this merge and then the plugin site was able to retrieve the real me of the plugin of this new plugin. So we're good. The artifact caching proxy breaks party moment repository. Between all the commands we add on the initial artifact caching proxy issue I've, we've missed a command from JC, warning us about some dependency artifact, not in my own central. So I have added the exception for elementary release and also shimmer release and some of our snapshots in some events settings. So the artifact caching proxy isn't mirroring this repository. Everything except this one. I don't know how we can easily, if there is a way to identify similar case of artifact not published in my own central. Maybe JC will come back on this. Yeah, I didn't bring him specifically so I think these three are the ones he listed earlier so we should be good. We would have seen if there were more no for now. Maybe. Maybe a week. Maybe. I don't know. We'll see. Let's see update of for instance with the last test version. No issue whatsoever with this one. Questions about this level build dependency was a plugin developer wanted to know how to use some people dependency. He, he's done that by modifying the Jenkins pipeline to run people style requirement.txt to install the BZT dependencies, which isn't in our image. So we're good from there. Bumster terraform module for AWS EKS. Damian worked on this issue and got some trouble with the custom volume on the node as the AWS controller auto-scaler doesn't automatically assign the correct node for the new pod depending on the custom volume and there was an affinity issue about it. Depending on the zone if I remember correctly. So we fixed that by adding not affinity here and or things on the storage storage class. And that's it. And the auto-scaler configuration. And he also added three. We know one person. So we are sure there is at least one node for each node in each zone. The next issue is about deprecated plugins. Dependencies, I think. And they have been removed from all our instances. And the next one is the move all of the, I don't remember. I think, yeah, Tim has been granted the manager access on this mailing list. Thank you Olivier to have taken care of that. Good. Now on the work in progress. The, I think that the terminate build stuck in Q on a fracy. We've noticed that when a fracy is about starting running jobs are stuck. In fact, that's cool. I discovered that by by clicking resuming it's it's going back like flawless. I don't know why they are both but therefore it might be an issue if for instance configuration or plugin. We don't know yet. I've been a fracy I restart some time ago. I didn't check it yet for the jobs. It needs to be resumed. It happened yesterday. I have. I've merged. I've done a modification to, to add. To force Jenkins controller to use the baby for on a fracy. We've received Jenkins at misery. Yeah. Things that was a problem. Some thread were stuck in IPv6. So merging this pull request for things the controller to use the baby for made this instance robot. So you might have some build to resume. Check. Introduce artifact caching proxy for CI. That's last Friday. I've. We've switched the bomb build to use the artifact caching proxy. I was expected and I'm now working on switching on making the run maven shared pipeline library function to use the artifact caching proxy too. So the remaining nine repository using run maven will automatically use artifact caching proxy, including Jenkins core. So what can progress too. The next two issue, add the private k8s and public k8s. We are planning to work on this. We were waiting for the weekly release. And one of the first migration will do is to move release.ca that Jenkins that I owe from public k8s to new private k8s. And the other services working currently working running on the other public k8s. But we will announce it on the mailing list before follow the major one like a depth. Realign reported Jenkins. That's all mission. Working progress to. We, I don't know if we received the last. See if there was an. I'll send them a reminder today. I assume that usually will I'll receive them end of day Monday or early Tuesday. Renew the senior certificate for Jenkins also like, like say one last one documents a good sign in certificate renewal process is ours to be sure we will work on it together and think with Mark and Stephen. Right, so will the three of us will get together. I'll schedule a session for that will will do it. I may even schedule it through zoom and record it. Certainly I won't publish the recording until after we've decided if the recording is safe and didn't disclose any secrets, etc. But, but there's no harm in recording it and not publishing it. So I'll get the back son version of our pain pain and tracks. We did not time to work on it since last week, but we still have to. And you plan to use that to make it. Tool yet multi guitar tool to mate as a pull request creation on each of these response during. This is the last one, the second page of the alert. I made a pull request on. So each of four Azure. The image and are now. We don't recycle them to reuse them. Five minutes after finished job jobs and he also increase. Increase this size from 128 to 150. And he also switched them to. Since we've got. Decrease in the world as your budget, we can allow this. It also will. Decrease windows build time. Which is. Which is why I. I keep this issue. And. In the. To do. Yes, we have. The working progress issue. We'll switch them to next week. We may have to bring up the, the one to upgrade the Kubernetes. If I'm not mistaken, it's. It's thought to be. Close to the end. I think. Okay, nice to. Yeah. Okay. Need to check, but I think. We'll work on this together. Yes. Don't think. No. Okay. And the background working on our not in the, in that desk. So my work is not shown. Can you tell us a bit more about it? Oh, yes. We discovered that the. Images from docker for the, the agents used by the Jenkins. We're not built. In fact, they were built. They were not published. And now I'm working on the way to. To have both. Docker. A or M and AMD. And I think. I managed that this morning. I want to double check with them. Yeah. But it's. It's not too bad. Yeah. For now it's, it's, it's a mess because there's my fork and. A branch in. Close to main because I need to try it as tags. To make sure that it's built when it's a tag. That's why there's two. Pull request. Which are. Close. If I didn't make any mistake, they are the same. Okay. I think it's all for. I just raised one. That I detected this morning. The. There's a null pointer exception. I reported as a help desk ticket. And if I suspected something that needs your help, because I think it's pipeline library somehow. Stable dash 2.387. The next LTS branch has been created. That's good. We like that. It's, it gives us time to three weeks before we, we actually reached that release point, but the job is failing with a null pointer exception in the pipeline library. And I suspect. We're, we're trying to, to call something that is, we're dereferencing null. And. It just needs someone to look at it. Okay. Oh, in fact, it's even, it's in with artifact caching proxy. So yes, it's, it's definitely in code that, that's familiar to you. Nice. Okay. Okay. I think that's it. Have a good day. Great. Thanks everyone. Recording should be uploaded. I hope within the next two or three days, depending on how I do it, getting things recorded recordings uploaded. Thank you.