 Hello, this is the weekly intro meeting. We start we are so pleasant. Sorry. Let's mark. We have Mark White, Stephen Mel and Bruno Verrachan. To start for the announcement, we have a weekly and two LTS release with a security release. No announcement, I think. For the current milestone, what we have done this week, we've upgraded my event to 3.8.6. It was suspended since there weren't any release in the GitHub repositories for the last version. So we switched our tooling to use the tag instead. And with this upgrade, we also make sure every repository needing this Maven version would use packet image as a unique source of trust for Maven version. So the current window agent and Jenkins as a pipette infrastructure are looking in the current image tools that takes the files. A user wasn't able to send in into a kunt, you help him mark. This is good. We had to enable rotation on pipette slug because they were far too big. And I don't have more to add. Next, we had an issue with update-enter certificate. It has been renewed manually by Damien, but then we had a report about error when Jenkins instance wanted to check plugin signature. And we noticed then that some crawler were failing. So they're signed, they're, they're retrieved by this crawler listing all the tool version where weren't updated. And so their signature were still with the old certificate. So even with the certificate manually updated. This is a JSON file weren't signed with a new one. So Damien decided to make a script to manually sign to trigger a sign on every existing JSON file. So they could be signed with a new certificate. And on my side I fixed two crawlers and make sure the other were working as intended. On the next, I finally put in place the notification on people on helpdesk issue. When a certain keyword, a certain label are applied to issue. So we could notify teams on people on the issue to make them aware of the current issue. For example, the crowding label is notifying the crowding admin teams. And we could also add a notification to Daniel when the update center label is applied. I have to ask him if it's okay with him. For the work in progress issue. We have the migration of update Jenkins to Oracle. The migration is working on the Oracle for integration. I think it's still a work in progress. For digital sound, we had a meeting last week with Ruby who managed this sponsorship program at digital sound. It was a great meeting and they have already renewed us with a credit of $2,700 and they will give us access to their sponsorship new form. So we can help them tune it and give them feedback. So it will happen at the end of June if it's okay for them. But yeah, it's in really good shape. Previously, we noticed the issue about PowerShell not available on every agent. And I intend to instead of putting alias or determine the availability of one or the other executable. I will install the last PowerShell 7 version on every agent and make sure also that Windows PowerShell, the previous one is also present. So all call to PowerShell or PWSH in pipeline would work. And I think something in that should be added to note the difference and to encourage people to use PWSH as its last one, last version. So still a work in progress. I'm putting it for the next Afro team thing. To evaluate for try condition to improve the stability of builds. It's about what Jesse has implemented. We have an incremental build already, but we'll wait this week to see how it works with Jesse. So I'm putting it in the next mic stone. To clarify on that one, the idea is sometime after the security release is installed on to ci.jenkins.io. You'll do some experiments with it or you're going to do experiments elsewhere. The thing is we have we have already installed the incremental build on infra.ci, but we have to have it also on ci. So it will wait after the security on which I think if we it has to be on all instances, there isn't anything to prevent the backline to be run on one or the other instance. And since it's concerned, mainly a plugin, we have to wait. Certainly since ci.jenkins.io is the place where we most often often see failures. It's a great candidate to do the checking. It really is. It's a good choice. Enable development integration in JIRA is about auto-linking GitHub in JIRA. It's open, but I don't know what it will be a Jenkins CI admin and JIRA admin who can do this kind of work. And I'll put it in the next milestones since I don't really know how Tamiya will deal with it, but yeah. This issue you opened, Marc, can I let you describe it? Yeah, so we've got a new system 390 agent machine available. I've been running tests with it for several weeks. It's ready to go. I just need to make the configuration changes. I still have and I'll create a separate ticket for this new power PC agent that needs a similar setup. And so I think if it's okay with you, I'll just create a new issue that is effectively a duplicate of this issue to do the same thing for PPC 64 LE. Yes, go for it. Put it in the next milestone. Yes, yes, please. Thanks. Sorry that I haven't made progress on it this week. Thank you very much for your advice. And the card height limiting. I think we still, we are still waiting for response from the car. If I'm not mistaken. So we have no progress. Put it in the next milestone. Great to keep an eye on that 22. Sorry, I haven't done much. We didn't have time to work on it, but we'll try to at least take some time every day of every week with the fun to review the officials and blog. We need to check together for digital ocean what I've done if it's good enough on that I'm not quite sure. And before going to the EL key version I want to make sure that what I did for digital is is good and enough, but I need to check with you. A little more info about digital. I've been able to reverted the request, which were disabling the digital cluster in our infrastructure, but I still have an issue. I'll put it manually in CI.chain. I'll see it. The last one also for next week. Yeah, this one is depending on the Oracle VM building. As a new issue. And Daniel opens today. An issue so we'll so we can to ask us to migrate from the workflow CPS globally the plug-in to the new pipeline for the lead. Where clubbies and I think that this extracted useful future. So it will be more light. We have also an issue opened by a deck about plug-in. An issue I also got when going on plug-in. The top menu doesn't work anymore. I'm not sure it's a good place for this issue. I think the best is actually to move it to the plugins that Jenkins.io GitHub repository. And I believe that's called plug-in dash site. And the next one. This is a new issue is one from my fault. There is an issue around weekly that's the CID Jenkins.io. He made a pair to update the description on the page and it's not taking an account. Another one I missed is the time stopper plug-in with activity in all instance. It's not taking an account for CID also. So I have to, I look around but didn't find anything. So I will look it with them next week. The time stamper configuration you said was also divergent. It was different on that weekly than on our other instances. It was only present installed on CID Jenkins.io manually. So we've added it. I've added it in the plugin that takes the list in all Docker Jenkins LTS and Docker Jenkins weekly image. But it's unfortunately not working on any on CID weekly. We have here, but not on weekly. I've tried a new build. It's not taking an account. I don't know why yet. Do you see any other issue we should discuss about? None that I recognize. Just the concluding reminder. Tomorrow's a security release. Be very careful. Tomorrow's a good day not to do infrastructure changes. Let them wait, let them wait until Thursday. Yeah. Yeah, and there is also an issue from my fault. But it's more about Jenkins. Repository. It's about having a predefined set of label for every repositories. And I have, it was, it's on my wish list for my Kitabas code issue. My longstanding Kitabas code issue. I forgot if we had fulfilled an issue for the data dog that we want to upgrade. But I'm not quite sure we would have time to do that during this time being. That we want to create. Can you a little bit more about it? You know, we want to make sure that it trigger page or duty on the specific case. Like for example, if there is two different area that have the same problem. And we will want to unify every check building. Within the terraform. Action and not a docker file. I think that if I understood correctly, the aim is to simplify and and do better check and maybe take advantage of what data dog is offering, because we are not using much of it. And I'm quite sure that we can extend the quality of the checks. But we have to find the boundary for that. It's long. Yeah. Yeah, it's a background task, but still we have to have an issue and to track it. Especially because we have a page or duty on top of data dog and page or duty is brand new. And we probably can have a specific page or duty alert. I think we can spawn page or duty with lower. Priority and stuff like that. Yeah, we'll have to discuss this. We'll have to look around. Yes. If it's, I don't see anything else. So on my part is okay for you. Okay. Have a good day and goodbye. Thank you. Thank you. Bye bye.