 Hello and welcome to the 14th of March, 2023. We are with Beno Bahrain and Mark Wraith. For the announcement, we have the weekly, which is built currently in progress for the container image publication. As of the announcement, I don't think we have any. In the upcoming calendar, we have the next weekly next week. Next LTS. I don't know when is next LTS, do you know, Mark? Double check, let me double check, but I think it's April 5. Yes, April 5. No security advisories for now. And the next major event will be, I think, the city hall. And Devox Schwanz in April. Oh, right, right, Devox France, right. Do you have another? None for me. Google Summer of Code is ongoing, but it's dates and timelines we know. Okay. So going to the issue, I'll start with the don't issue, I'll go to the milestone. The first one is the Jenkins CIA transfer organization verification. So we've got it's nice batch to show it's an official organization. For the repository transfer between developers and official Jenkins CIA organization. We have a login issue with a user with plus something in their mail. Who did, who could not log into Jira. They changed their email and the most plus something and works fine. Nothing to add there. See job copy builder. Was an issue from last week. Was an issue without the update center failing. I've closed the issue since the dependency was correctly published after that. Stefan made an update manifest to upgrade the automatically is a quota of agent we are using on the CIA test cluster on the digital assembly cluster. So when we upgrade the value in as code in terraform, it automatically updates. See available quota for the agents in our CIA configuration. So does is that why so I've seen for instance right now there are bill of materials evaluations and running on CI Jenkins that I and there are 400 agents allocated and that's significantly more than before is that because of that change. In part, what is the main reason we could have some we have we have now as much as as much as we have the same number of agents on digital ocean than on AWS, because we upgraded the wardrobe limits. In the digital ocean I couldn't. We went from 25 to 100. So we can now request a lot more agent. So now, each of these cluster can, can have 150 agents each. So friends. And you can see that we can have, we have a better capacity in CI Jenkins that I have. I don't know if you saw that but I have added this link so everyone can consult the current workload on CI. Oh, good. Thank you. I think normally available in the manage Jenkins section, but as it doesn't require an authentication for being served for looking at it. So I put it in the public section. So everyone can check that and see why the ability is not running. And this is a boom. Next one is a step and replaced the GitHub action with a dedicated Jenkins file for running a big key on Jenkins on the public repository. So the next one is a request from not my fault to install a renovate on the core of the trip or generator. Mother for adding a basil has a mean to the Jenkins I transfer as he is responsible for many transfer recently. He is a request from not my fault to remove the module folder and say the Jenkins that I own. So remote it seems every repository in this folder where archived since last summer. Right, right. Okay. I was wondering if there is a way to know when Jenkins ID for repositories are kept. But yeah. It should be good to do something up to remove some jobs, maybe. That's fair. Again, to Jenkins. It's another plugin, which moved to the Jenkins organization. I don't know if the monitor was last week or. So that was the done issue. Not in this milestone because I haven't closed it yet, but plugins, plugins site wasn't updated. It's not an issue with logic fair. Not working on the pipeline. Because yesterday I validated the renovate request of the things in the image we are using to build plugin sites. So this version was using people free dash to install the CLI. And since dependency work logic fair. So I switched to the devian package to install as your CLI commands and run test. I want to build manually on master branch of plugin site with this new image and it works successfully you put them that mark. We say yes. I'm running in the last version, but based on. Next, we have any questions about this issue. None from me. Work in progress. Just a little notice. Some are waiting for them and Stefan come back out of office until Thursday so most of them are waiting for their fortune. This issue should be. I have to check with time if we had a separate kit of action to, to manage the release of this repository, or if we continue to use one. Also, really taking care of the Jenkins IO components release. It was the IRC but used for the meeting when they occurred in IRC in a long time ago. It's not used anymore so we have something to do in the pet repository and archiving the repository. We're going to go to Jenkins.org mission. We want to say what about it now. Sorry, what was the which one was it again it was. Thank you. Oh, yes. Yes. So, thanks. So, so the, the progress there is that we are continuing to try to locate the owner of a Chinese IP address that's making heavy use of our bandwidth, and it's unnecessary heavy use. It's also been well artifact caching proxy is doing great. We are behind schedule on deploying authentication, and we need to do some additional log file analysis to really confirm that authentication will actually help. And also crow noted to me that there are some hints that in the logs that adding authentication may actually not not really help. And the goal is reduce the data transfer, not implement authentication authenticated access so we've got to do more research. And the next one is about artifact caching proxy. I've got so many as a repository with. Let's see. Working on it. So next one will be the generation. And I've also added the request to monitor. So that's the volume on every cluster we have. So we won't have the issue of one of the full and using requests. So that's something to add about that. So, I had a private case cluster. Last week I made some regression of free bots, which were remaining on the product. Well, and the next step is the next and final step is to move release.ci on the new cluster. I've done the preliminary phase. I have working instance and working controller on the new cluster. I've checked backup restoration without any credentials so no job will run. And I have now to do the announcement on the concrete regression. And no, we should expect you they should take one to today. Most hopefully. I'll use a signer certificate for Jenkins. I can I let you Yeah, yeah, so the there the submission has been we've submitted the request to Digisert, but Digisert had an additional authentication requirement that requires a legal document from Linux foundation. I'm suggesting that the continuous delivery foundation is part of Linux foundation, etc, etc, and it is allowed to chain off of their authenticated organization and right now the lawyers are working through that authentication process we did this process three years ago. But my mistake here was I should have started this process much sooner, because the lawyers don't always go as fast as we'd like. The comments are good signings as you get a new world process so we have to initiate. Right, we'll, we've we've captured screenshots and we'll we'll add to that documentation as we complete that task. I'm going on the side of Jenkins. We see additional capacity on the Jenkins that you which shouldn't be a problem. Yeah. Yeah, I've definitely, I've definitely not seen any hangs. But then again I didn't see it before. So I wait to confirm we can close it but it should be good. We want, I think we want to prioritize or not see bomb build against the other, as it was suggested before. Right. You can't access for plug-in account. Plug-in issue I think the user yesterday, I'm waiting for their response. As a credential for certs, yeah, I don't remember what was what is the status of it. Yeah, I think it's a long term. We have to implement. Yeah. Maybe I'm a long term fix. Well, and if I understand correctly on this one, it's this will actually let us avoid using a credential at all right it's some other thing that then works inside the context where it knows it's executing in Azure. I'm not sure I want. I didn't put all that much issue so I prefer to let them explain it. I did some touch job is fading. I think it's almost ready. Yeah, I would propose we'll go ahead. I was just thinking we let Damian decide when he's ready to close this one because he may have action items hidden in this that I think it would be unwise for us to close it. We'll decide when he's ready to close it. Yes. I don't think we made any progress on it yet. It's time to check on that. So we really put it in the next milestone. Out of space on the for the bomb build. A lot of the building because of that. Thank you. Thank you. Yeah, just for info there are now 14 pull requests cued on the bill of materials repository. And, and that's about triple the size of the merge queue of the pull request queue that we usually have we typically have zero zero to two, and in a bad time it gets to five. So, so we've got some backlog to recover once we get this resolved. We have limited access to release that's here to secret between Polska. It has been postponed because we had a week last week with so security release the tool to SMC weekly. I think it will be done in the next milestone. Before or after the BCI integration. We have a child package that found on build agent. I have to check with them now for this one I don't know how to to resolve this issue. We have this dependency on the factory. We have two first one, but not six. So I don't know why and I don't know where it's produced. And so I don't know how to exclude them from the packaging setting. So yeah, I have to check that we can get a new credential for Parker as code is there a form I think Stefan has almost I've almost finished it. Secret and show this successful I think he is a little bit so when he's a company. It's this is a new shoe about the description of the drinking scene with a chance. It's a little bit confusing as the it has the same notice as the car slave agent on the car. It has to be updated. I don't have the access to do that. So that's who Damien or another Jenkins. Then we have an occult request. I don't know I have asked I've asked this result to try again because I don't know I don't I didn't see anything in the log so I asked him to ask this person to try again. This one is thrown and she's sure about CSS that's great for PKG.org in the Jenkins.io I haven't looked at that yet. It will be for the next milestone. And on that one I have to warn I don't I truly don't know why I put the monitoring in the SSL certificate because I don't see it referenced anywhere. But but usually when I put a monitor in it's because something mattered at some point. Yeah. I have it. I don't I don't think I'm going to have time to because the the signing certificate is is such an urgent thing and other things so I'd leave this one as is if it were to expire and someone complains to us because we didn't have time to do it. So I'd leave this one as is if it were to expire and someone complains to us because we didn't have time to do it. Okay, we'll we'll learn it won't. We know how to renew certificates right it's it's not a. Yeah, and I suspect it's just a configuration change needed on PKG Jenkins.io that it's it's somehow lost its knowledge of or, you know, cert bot is doing something odd, etc. Yeah. Okay. Back to the note. Why it's empty now. Okay. I don't have any particular issues about loud to speak about. Because we see that next week. It's okay for you. Great. Any question about the issue we reviewed. None from me. We look forward to getting Damian and and Stefan back. And I hope to get that bomb disc full thing resolved. That was on my mind. Okay, then see you next week. Thanks.