 Okay. Hello and welcome to this Jenkins weekly meeting and Jenkins Safari weekly meeting. First we'll do the announcement so see two that free free two weekly release has been delivered. We need to fix a missing tool. We emigrated the Gira issues to GitHub issues. There is a dedicated issue in the help desk repository to see progress. It's almost finished some just some dark missing some updates. New Java release are coming. JDK 8, 11 and 17 referring to Temera progress report. On the notes I'm almost I've almost finished digital form repository to create a cubanet cluster. There is a nabless issue. It will be an agent supplementary agent for CI. Jenkins.io and I'm going on two notepools. One with only one node on the smallest size and one other with more fishy node and auto scaling enabled. So we will be able to increase the size of this node without having to recreate the cluster. So it's why I've got two notepools and also because there isn't any possibility of zero scaling digital notepools. And the second pass was using digital ascent VM agent for CI. Jenkins.io. We'll see later if needed. After digital ascent will be finished I intend to do the same on scale way. And there is also an issue and I will need to get access to the account. I have to see with Olivier and Damien. The work on the pre-baptized cluster is still a work in progress by Damien which is currently in holidays. And building the current image on CI. I think it's Stefan works currently finishing it. And for there is also an issue we'll link it to the meeting notes after. On infra CI credentials and CI Jenkins.io timeouts I think it's Damien was working on it. I don't have any additional information on them. And for the Alibaba mirror we didn't receive the answer to my questions but we'll add it anyway. So I wanted to ask, check with Tim, Tim, any objections from you if we add the Alibaba mirror as another mirror in addition? I think it's geographically it's Central US so it'll help with the load in North America. Yeah. Did they ever reply and say why it was CI? They were getting our replies and I replied back to them directly. I'd never heard from them. Yeah. Go ahead. They created another thread in the mailing list asking the same thing as the first one. We could just add them Okay. Yeah. I mean it would be no harm to have another mirror even in response time wise it seems like it could be in the Central US so it may in fact be accurate. It responds to ping almost as fast as the other mirror does that is lists itself in the Central US. I'll try it. Okay. On census.junkins.io, Damien still has to ask Taylor or Olivier about what it does. And on the whole day-to-day operation it's almost the same as last week. We still have to disable this spam for certain on Trusted I think I don't remember. And I've started looking for the to update the CASC section for CI.junkins.io Outs with the Matrix Outs plugin. There are still users and groups which are ambiguous and need to be precise. I think that was even concluded by our meeting last week. Are you okay if I just delete that from notes? Yeah, I think it's completely okay. And there were a lot of traffic on ci.junkins.io and the IP address has been banned. We have to replicate the manual change to ban it in the AFRAS code. Well, yeah, or find a better way to do it. I'm not sure if the technique I used made any sense. Using IP tables to block something is very low level, I think. And Gavin was even worried that it may not work depending on the routing systems that are being used inside that to reach that machine. But it did seem to work, so everybody you and I can work on it separately. You can probably download it at the Azure level if there's any SG on it. Sorry, Tim, could you say that again? As soon as I could have done it at the Azure level, probably. I'm just checking. Probably simpler, I would have thought. Yes, and Tim Gavin had suggested, hey, we've already got a bunch of redirects that we use at the Apache level where we redirect certain API calls to the BitBucket. This could be another example of that, but I didn't see an obvious pattern of which APIs were being hit. It was some RSS and some others. Yeah, sounded like an RSS where you're going about cane. Okay, back to you, Eva. Yeah, so it's in the show up and we'll see how we'll deal with this. I don't know if there are any questions or additional points. There's a public network data tier security group that you could block people on in Azure. So you said there is a public, say that again, Tim. It's public dash network dash data tier, no dash between the data and tier. No dash between the, okay, there. Yeah, so it's a security group in Azure that you could block people on, probably a little bit easier than IP tables. Okay, great. And that would be, is that something that is managed as code somewhere, would that also be a, we would do it interactively? I think it's, I don't think that the net code works these days. So there's code in the Azure repo, but I don't think it the terraform is used right now. Okay, great. Yeah, you'd be able to change it interactively anyway. The terraform would be highly unlikely to roll us back. Okay, excellent. Thank you. Good, good guidance. Okay, then it's, it's look, if there isn't any other point, it's good for us for today, I think. Thank you. I'll post the recording of the meeting, hopefully within the next 24 hours. Aravay will look to you to put the page up on community.jankins.io. I'll send you a link to the video recording when it's uploaded. Perfect. Thank you. Thank you.