 Hello, this is the implementing of the 6th of September. We are me, Mark White, Stefan, Merle and Bruno Verhan. We don't have any specific announcement to make. For the coming calendar, the weekly is in progress and 2.261.1 LTS release will be tomorrow. The next security release will be on the 21 of September and as the next major event, we have the Jenkins board and officer election. In September, we will end some accept nomination. In October, we will register the voters. November, cast the vote and in December, announce the result. Damien, as an officer, will certainly run the elections and we will see with him as soon as he comes back from PTO. Any other announcement or calendar? On the Jenkins weekly and possible impact on the LTS, I've had reliability problems with GitHub today and so I'm a little concerned that the weekly may be disrupted by GitHub unreliability. I'll do checks on it after meetings and today. I don't know the current health of the weekly. I hope it's in progress. I've seen some indications that it's been published, but I haven't been able to do the check list yet to confirm that it's actually a good release all the way down. Okay, so for the issue we've done this week, there are a few. Danielle took care of adding mirror URL for two repository, artifact repository and there is a private discussion we'll have with Damien and him to know if we should have access to the artifactory so we can manage this kind of issue ourselves. Basil has opened another issue related to yours about a repository. It seems to be a very little repository, tiny repo and I don't know if he asked Central if he can publish on it. So I didn't put any milestone on it since it's not really we can't really do anything. I let them discuss. The other issue we've done was adding maintenance to a repository on GitHub. So I've used the IC bot to do it. In the working progress issue, there is a new issue I've asked for this user to confirm me has access to this email and when I confirmed it, I'll be able to delete his account. I checked on the repository permission update. He isn't the maintainer of any plugins. Ask me about asking us about hosting a plugin else scoring application. I've saw it with him. We made a little improvement to the library to be able to retrieve a stashed artifact. As he was building, it's a Java application at the beginning of the pipeline, then calling or build a current published image shared pipeline library. But this function is doing a checkout at its beginning and didn't retrieve the stash artifact like the chart and the profile. So I've made an improvement to the pipeline library. And we saw it work as intended. We now have to add the plugin else scoring repository on the the curve. But we don't have access to it. We'll add us to this account, but we don't have access for now. So it will wait. I also ask him to make an end chart. And he is doing it. And we'll add it to the end chart we have on Jenkins and so far. And when such end chart is ready and the repository created on the curve, we will be able to deploy it. I think on product public k8.8, but I have to confirm it with Damian. And the collect data metrics for FM Ralf virtual machine. I'll let Stefan. Yes, thank you. I did some progress concerning the Azure part with the Azure VM. I got agents for tests working right now and spawning data doc agent. I worked on the version of on EC2. But I'm stuck right now on the cloud in it. That was not starting and right now is starting without a really understanding why. So I'm in a good way, but not knowing exactly why. And the last part is with the Kubernetes and the Docker side of that same agent. My problem here is with the path and the environment variables. So it's still a work in progress. And we'll see if Damian can find a few solutions on there. For the next issue, the Jenkins release Twitter account many weeks behind. I've looked around the LVR.IT account and Twitter field. I've sent them an email and they answer as they respond. They can change the email, but just for one with Kosuke domain. So I've sent an email to Kosuke asking him if he can retrieve the account and change the associated email to provide a hot one. I'm waiting for response. This issue, I don't have any progress since last week. I have to ask for Damian what it's about. We didn't make any progress on this issue. The containerized Java 17 windows agent. I don't know, Stefan, if you made progress on the all-in-one image. No, not at all. Okay. And finally, reintroduce an artifact caching proxy for CIDA Jenkins.io. I've made progress. I have a working proxy on Azure. And I'm now looking at creating one on digital server to have one on two different providers. And then we'll probably have to tune the engines configuration, the proxy configuration. For now, I've made some measurements and I'm in the radar similar to the central repository. I don't know how much it's caching. I don't know how much the caching reduced the bandwidth yet, but I will measure it later. And if we are going to the new important issue, we didn't add any issue to this list. There is some new issue, but I didn't put it there because I don't know how to act on them yet. Like the windows agent, which take four to five times the amount of time compared to Linux for the tests. Three times. It's good enough three times. Yeah, but I don't see really how we can resolve this. As it explained, you re-enabled some tests for windows and it's a reason now this test takes a long time. And Danieli is suggesting we might want to publish incremental deployment as soon as the next build are passed without waiting for the windows one. But yeah, we didn't take any action on this issue yet. And I don't think there is also this issue, but I have to ask Damia what this is about. I don't see what we can do on it. And that's it for the issue of this week. And do you have any questions? Not a question, more an observation. While the meeting was happening, I've seen that the data dog alert has been raised that the windows installer is not available. And so that hints that the weekly build had a problem generating the windows installer somehow. And so I'll have to do separate investigation afterwards to understand what went wrong and what we resolved, whether it was a GitHub hub problem or some issue in the build scripts unknown right now. I can see there's an error and I'm proud that our monitoring detected it. That's really great. And it's nice you said it's ready to say weekly release because I wouldn't have made the relation between them. Right. Yeah. So that monitor is raised if a new version is released and the corresponding windows installer is not available. Whereas I'm happy to announce that the Debian installer for the weekly release ran successfully and performed the install. Or no, the Red Hat one did. The RPM did and the Debian one is running now and is looking just fine. So it appears to be somehow specific to windows and so need some investigation. Okay. Do you need any help on this investigation? I don't think so. At this point it's just a matter of time and I don't think it's a crisis. So there is what will happen is users who go to Jenkins.io right now and attempt to download the weekly windows build will get a not found page because it attempts to download the new version and the new version is not available. And so if you get bug reports, if we get help tickets that are raised saying, hey, the windows download is unavailable. Yes, it's known we're working on it. Okay. And if you'd like I could raise a ticket but I wasn't going to raise a ticket unless it persists for an extended period. That seems fine for me. So Debian did not build with the most. So there may also be a Debian issue. The Debian build that should have done 367 instead chose 366. So more investigation needed is all I need to say. Okay. If there isn't anything more to add, I will say goodbye and see you next week.