 Hi, welcome to the weekly team meeting, intra-team meeting. We are the third of January 2023. Most of the team is on PTO right now. But you got the best with Marc and Bruno and myself, Stefan. For the announcement, we have the weekly that is right now in progress, 2.385. The change log, I think you're done, Marc. Yeah, it's published, but it needs revision, right? It needs improvements. OK, and we are waiting for the end of it. We have to watch out for the intra-team, for the signer certificate that will expire on the 30th of March. The code signing, yes, we just saw that with Marc. That's just a reminder for us not to forget to deal with that. Is that OK for the announcement? Do you have something else? No, that's all. Well, that's it. The other announcements are on the upcoming calendar already. Yeah, the next weekly will be the 2.386, if I'm not mistaken. And it will be on next Tuesday, which is the 10th of January. For the LTS, I don't have the date. So thank you, Marc. So the 11th of January, the day after that was the 2375.2. Yes, everybody who wants to test it is more than welcome to do that. Next security release, we don't have any information about that, I think. And the next major event may be the first day. Is that right? Yes, and that's in February, right? 4.5, if I don't. Yes, you're right. It's not the recent day. Yes, I need to buy my plane ticket, by the way. So as for what I've been doing, I remind you that we were on PTO. For me, it was for the last two weeks. And my co-worker friends were all on holidays last week. So we haven't done much. But still, oh, thank you. So is that the, oh, for the close. Why, yes, sign it, luck. If you prefer working from the HackMD document, we can stay right there. No, the problem is that I don't know all the issue by heart. And I need to review them on my screen to make sure that I'm not seeing anything wrong. What I've been closed is sign up link. Oh, that was that. Oh, you should show the detail from the sign up link, the first one. Okay. That people will understand what I mean. They had a little hiccup on the text and on the sign up. And they did change the code and JavaScript, if I understand correctly, function to update the text and to make it working with Safari Firefox and Chrome. So it's done. Good work. Oh, oh, good. OK, so all right. OK, so he's, I haven't rechecked. So that's great. All right, thank you. Seems that you have changed everything and achieve and each plaguing long enough to duplicate it. That's from you, Mark. Right. And that one's that one's done. Thanks very much to the infra team for helping with that. We what happened was there was a service or no, there's a component that the maintainer said, I'm no longer maintaining this and a plug-in that that backed it that that the maintainer was also obviously no longer maintaining because they aren't maintaining the code that the plug-in used. And so we we deprecated it. We didn't suspend distribution because it's not a threat to the infrastructure. It's to users or the infrastructure. It's just no longer being maintained. So deprecation is a good way to clarify to the users that look, there's no maintenance happening on this and then we'll happen. Good, good. I know it was the MBM release. To the G frog, oh, G frog at the at the huge maintenance. So maybe it's that in between my savings of it. So you did hence what the problem mark and that was a configuration in the savings, if I understand correctly, OK, good. So, and next one. Workflow API plug-in that was not a Jenkins infrastructure. So they explained where to publish this question. So it's closed because it's not as. Merge, but not my fault, closed it. So he probably did something. We don't know in charge of plates, right? Right. He did updated the SEM repository permission. So OK. And this is just another another account account mistake, right? Yeah, probably at the wrong server and they probably found that. Right. Damien said, look, you're this this has nothing to do with Jenkins info. Yes. Yes. So what's opened still open? There's the real in the repo Jenkins CI.org mission. It's a huge work in progress for mostly Damien. And he was expecting the. Yeah, we had a meeting with G frog, but they did. They did the migration during the holidays. So we will probably have some news and some data and statistic or next week. I'm assuming. Well, actually, it's a reminder. I have the action item. I haven't sent sent the request yet. I need to ask. Let's see. Where is that one on the list? I let me let's see. Let me make a note here somewhere action items. So this one is mark, wait, request, bandwidth, use reports for for repo Jenkins CI.org in case there are some heavy users we can ban by we could block by IP address. Yes. That kind of thing, right? So if we can find some easy wins, we would love to do that. Then we don't have to then that those those are a benefit, but we couldn't get those reports from the previous system because it was unfamiliar or it was it was not readily suited for bandwidth reporting. We hope their new system is more convenient. And but I need to ask ask them for those reports. That's not something we get automatically. OK, for the second one that add Windows to me 2022, that's my task. And I did prepared Windows 2022 back your image and an agent and CI Jenkins IO, but only one Azure for now. I did try it directly. The usage and it seems to be working. I did try this morning. I will try to find some other experiment developer to try it more further. And then I will probably try. But that's that seems to be not easy at all to have it working in AWS. Damian said that there were a lot of blockers. So we need to check out. But the one for the agent is up and working. The next one is at cluster private KITS. It's the main task for LV. They did a lot during the week I was out. I saw that the VPN is working now. They managed to log in and to use it. The next step is the big step is the migration of all the service that need to go in that cluster. And that's for a reminder that the aim of that project is to avoid the overlapping of IPs and that overlapping that we have right now on the current infrastructure is generating problems. And during the holidays, one of them we had to do something on the LDAP because of the overlapping. So we were eager to have that new infrastructure. Very good job primarily, but not done yet. So I will I will move all that to the next infrastructure. Milestone. Mirror stats reports, wrong results remind me that one. So let me just open it. I think this was was that it's listing. It's listing the we need to check out. We have to check all the mirror to know which one are really not used anymore on the one we need to re enable and and maybe to find a way to monitor all that. Right. That's also so as an example, this one, Yamagata University went offline about 24 hours ago. I had assumed that they were down for maintenance, but I'm a little surprised that they're still down. Now, the the one that is a little more surprising is this one that's duplicated. If we do mirror stats, rather than mirror list, it lists, oops, no, not mirror, I stats, mirror stats. It lists. OK, the servers we know about, right, Akhen, Exmission, Singwa, Savannah, but it lists several servers that I think we know are offline and probably shouldn't be in our stats. So so there's more cleanup needed, I guess, is the answer. And that's the last comment in the in the issue of Damian is saying that we need to to check the status of those force. Right. Exactly. And and this the the there is another surprise stuff on which, again, is low priority. I'm surprised that Cervana here is lower priority than archives. The the way that it had originally been intended was that archives would always be the very last, even if it's geographically closer. OK. And it's not that it's harmful because I will certainly never get to a to the sixth choice. Right. I mean, all we've got so many mirrors that to the issue or archive that Jenkins that IO is not the last proposal. Right. OK. Comment David. OK. So the wrong media chip, I think it's almost done. Yeah, I think there was there were one or two changes and still needed on our own servers. And that was what was still pending. It was archive. I think it did OSU OSL is done. But oh, so I don't know. I don't know. We will leave it open to check with Damien. But for me, it was all done. So maybe maybe I'm wrong and there is someone or OK us leaving it. But yes, I thought it was done. Yeah. OK. I closed it and then Damien reopened it. So I assume there must be something he knows that still needs to be done. Probably. So the next the next one is Netlify site for Jenkins IO component. Yeah. So so Gavin Morgan has created for token. I don't know which token is talking about. So it will need to wait for next week. OK. But yes. Should be should be an easy one. But the terraform module. This one I read if I read correctly, Damien was kind of not happy at all with AKS and spend a lot of time to update all that. And with new problems and in the finish with the with the certificate problem, because the well known Akmei challenge is not correctly handled. So so it's fighting on that right now. And that's not something easy because usually it's working. And right now it's not. So so it's it's a pain in problem. And the last one you see baseball baseball. Oh, I think we are waiting for confirmation from Mr. Dispader because Damien did reset his account. So he's waiting for the the opener to confirm it's two weeks ago. So I think we will we will close it. If you're OK with that, I'll close it now then. Yeah, but put something. Yes. Thank you. Thank you. That's all. That's also in the in the notes. Or the backlog. Do you want to review the backlog? I'm not sure it's useful right now because none. I don't have anything that would motivate me to look at the backlog. I'm I'm happy to open it up. If others want to see it, if there's something you say, oh, we want to flag that as that needs to be in the plan, get me work in progress. That's that's something else I can see. For example, the 10 private KS cluster backup is not something that we will do because we will have to to back up the new one. So so that we change the issue we say that the title will change and the aim will change. No, there is there is not much that we can do without everyone. Yeah, we've we've got plenty of work in progress already. I don't see any any of these that say, oh, let's we must bring that into work in progress this week. I think we will have to clean a little that that list. That's a war by itself. No, I'm sorry, that was that was a fast one. That's not a sorry thing. That's a great thing. Well done. So thank you and have a great year for two thousand twenty three. Thank you. Bye bye.