 Record. This request recording permission from the meeting host. So, can you mark, can you start the recording? Apparently you are the are we recording? Yes, perfect. Hi, everybody. Welcome for this new Jenkins infrastructure meeting. So, this time I have some good news. So, the first one is obviously related to the DACA hub. So, we got approval from DACA to be sponsored for the Jenkins organization, the officer proposed to sponsor, I mean, to wipe out the organization. So, I asked for the Jenkins for a value and the Jenkins I am from. I haven't received an answer yet for those two, but yeah, I guess it should be fine. The thing is right now is I cannot confirm that it works on my side because the user interface is the same than previously. Nothing gets changed. So, I'm not sure how I can test it at the moment. But yeah, the most important one is that we got confirmation from DACA that it should be working, which is great. The next topic is related to the DACA images for Windows. So, Garrett made some great improvement there. So, maybe Garrett can explain a little bit what you did here. Yep, sure. So, I have just whilst the PR for adopt OpenJDK is still open and sort of unmerged. So, we have forked that repo into Jenkins X Infra, sorry, not Jenkins X, Jenkins Infra. We have tweaked the build so that it should build on our slaves. So, that actually works and those images are being pushed up. There's about 12 notes, a little more. Actually, I think it's 16 images that it pushes up into Jenkins for a value and JDK. And I'm just doing some tweaking to make sure that the tags are consistent with what adopt OpenJDK are publishing on their site. And that should be done today, what I thought. Okay, thanks. Just some clarification here. We decided to move with Jenkins for a value because we don't want to officially support those images. So, we just, you know, to keep working on the Windows images without being blocked by the adopt OpenJDK projects. So, there is no expectation on how long we maintain those images. Again, those are at the moment meaningful testing purposes. They're all based on Windows 2019 LTSC, all of the ones that we published. The next topic I touched, I didn't receive any updates, which is regarding Gfrug and the work being done on repository in Seattle org. So, maybe Mark, you have more information there. I asked Daniel, but I didn't receive information there. I do not have any additional information. Neither Daniel nor I, as far as I know, have made any, have done anything yet. No progress this week. Okay. The next topic is regarding your JIRA testing. So, last week, we did, we tested the new instances provided by the Linux Foundation, same team and all the other people involved here. You spot quite a lot of bugs, but again, I don't think there was some major issues there, which block us to continue immigration to the Linux Foundation. I don't know. I guess we are still on track to plan the migration next week, but we still have to align with the Linux Foundation, folks. Yeah, I'm nervous about that one right now. Olivier, just because I've not seen anything from them confirming that next week. So, I'm going to launch an email conversation with Andrew Grimberg and with Anton Baranov to confirm that they are really good with November 9, because if they say they're not good with November 9, the following week is not a great choice. If I remember correctly, the following week risk collision with, I know the preceding week collides with a potential LTS. The following week was also a problem. So, I've got to check with them. I will check with them and report back by email to the Jenkins and from A-Lingless. In the worst case, I would be more in favour to reduce the announcement periods in order to do it next week if it's possible, because I would prefer to not delay the upgrade too long, especially all the work that needs to be done on Jenkins project in the following weeks. Great. Okay. So, that's good guidance. I will take that and we should push hard for the week of November 9. I think it's totally fine to announce it a few days before that we are going to work on. Well, and we've announced November 9 almost a month ago. So, it's been announced. It's just a reminder, hey, this is real. We will make this transition. We'll be down on the following day on this specific day of that week and that I don't have for them yet. So, the next topic is about the Azure bill, which is a recurring topic. The good thing is it has been paid last week and we started another discussion with the Linux Foundation to see how we could prevent that to happen in the future. So, they proposed to migrate the Azure account to the Linux Foundation. So, instead of being the owner of the accounts and asking the Linux Foundation to pay the bill, I would transfer it to the Linux Foundation, which is something that I would like to do since the beginning. And I think it would be easier to maintain it. But, yeah, we still have to engage the discussion. In the past, the reason why we didn't do that in the past was because I think they were not using Azure on their side. So, it would have been the first Azure account, but apparently something had blocked there. So, if I can transfer that account to the Linux Foundation, I would be more than happy. So, yeah, the next topic is about Azure credits. So, on that side, I think it's Mark. You may have some information there. No further feedback and they did not give a timeline when they would have closure on that. I'll share. We'll leave it on the agenda and I'll share if we hear more from them over the course of the next two weeks. Okay. The final topic that I want to talk is that I started working in the release environment again. So, I had a bunch of open PRs before I leave, beginning of August, that I'm now trying to test into what it is. So, the thing that I'm trying to introduce is unit testing, using bots, because the release script is getting quite big. And even me, I forgot what I did a few months in the past. So, I really need some unit tests, but yeah, that's the main thing that I'm working right now. So, Olivier, you didn't announce the big one. Come on. Merged, in from 910 to the master branch and released a weekly with it and it was all great. Yeah, true. That's indeed a great achievement because we had that our branch open for almost a year. I think I opened that branch last year in January. So, now we should be able to, yeah, that's a great achievement. We have, we still have few open tickets, then we'll be able to close the release epic. So, the main thing that I'm, that I still, that I'm still pending is so I'm working, I'm modifying the scripts to guess more information based on the branch. So, the idea is, so that's what I'm currently testing with, but the idea is, if you trigger release from the master branch, it assumes that you're doing a weekly, if you're releasing from a branch named security-2.235, for example, security that, so then it assumes that it's a stable security release. And so, this kind of information, those are explained in my PRs, and yeah, that's the thing that I really want to be sure that it's tested working correctly. The second element that I would like to finish is really having a full promoting workflow. So, the idea is we would be able to build every packages in advance, let's say a few weeks in advance, or when we, whatever, and then the day of the release, we only publish them. The current situation, and that's one of the reasons why we identified Windows issue really late last time was the, for some reason, the release environment was broken, and we only detect that at the last moments. And so, this is something that I would like to avoid in the future. And those two things are the most important one that I would like to finish before moving over on other projects than the release environment. So, for the two, I have open PRs that I have to finalize. Another topic that I forgot to add here, I also sent emails. So, I also work on the release. So, basically what I did was to reuse the email addresses from people who voted last year, and I sent them an email using sacreds. And I also worked on retrieving email address from people who have access to repotagenkinsia.org. So, the idea was to be able to reach the plugin maintainers in order to remind them that it's election time. I have a list. I wanted to wait for the first batch. I wanted to wait to send the first batch for the voters, for last year voters. Now, I think it is perfectly healthy on U.S. election day for us to send an invitation for people to register to vote. So, okay, later is fine, too. It's kind of, as a non-U.S. citizen, I cannot really send a message. I can't forget to vote. Don't forget to vote for Jenkins governance. Oh wait a sec, that has nothing to do. Yeah, got it. So, yeah, just, I hope you already registered for the election because it's coming. And, yep, that's it for me. So, is there any last thing that you want to talk here? Otherwise, I just propose to go back to RSE, which are all good. So, last call. One, two, three. Thanks everybody. See you in RSE. And let's meet next week. Bye-bye.