 Welcome everyone. This is Jenkins info team meeting. It's the 19th of July. Thanks everyone for being here. Let's proceed. We've got topics on the agenda. We've got announcements upcoming calendar and the notes from things that are done. Thanks to air they for generating that done and work in progress automatically we love automation thanks very much. Any other topics that need to be on the agenda other than the topics that we've already got. Don't think so. Okay, alright. Then let's go ahead so by way of announcements. I had the note that weekly has been released today the release checklist is almost complete. I've got a check that the MSI file installs everything else past Docker images have been generated etc. The release team so Tim Jacoma sent the message inviting people who are interested if they would like to be the Jenkins 2.36346.3 release lead. It's a good experience to be a release lead. I don't know why Google groups is not responding but if you're interested just reply to that message that's linked there. So upcoming calendar. This is a response to our to be sure that we remember remember what's happening 2.361 next week next Tuesday. Next LTS is to be sure that we have the calendar correctly July the. The RC release candidate 2.346.3 RC on July 27. 2.346.3 release. On August 10 is that yes August 10 and next security release has not been announced or hasn't not that I know of. So I'll have to check that next major event scale 19 next but that's not really relevant to. So that's all that I had any other upcoming calendar items that we need to be aware of. I'm not that I know but I thought the security release were not publicly announced. There is a they will give an advisor that will give a pre announcement a relatively few days before. Okay and and so once they've announced something publicly then we will state it here as well. Okay. Yeah. All right. Other topics then notes. I'm not sure how we'd like to handle the various done are there items that you'd like to highlight on the the backlog that's complete. I think this is a really great presentation because each of these links to the thing right so when I go here. There it is. Here's that ticket and I can read it in detail. Any any of these done items that you'd like to describe or or tell it say more about. And maybe we should took them by by order. No. I think we can sell those. We're moving embeddable bit statue plugin because you you took the lead on those on that plugin so it's it's not. It doesn't have to be removed anymore. If I'm not mistaking. Yeah, that's what I understand and that also lets us avoid this self hosted shield that I own instance so that's a that's a positive. Yeah. I have no clue of what is archive analysis test plugin. So I think this is just a plugin that had had reached end of its useless live use useful life. And so it was turned to read only. Okay. I have a strange to talk with we don't hear you are there. I think they they renewed the token for Jenkins on digital ocean. I should click you will probably be able to have more information that. Yeah, and I, I wasn't worried about the details there I think if people are interested they can certainly follow through the details. Are there any of these that are of significant note that we should we should look at them and say oh here was something that others should be aware. The fact that for the upgrade to come and test 1.22 we we had a problem with the secrets namespace but I think we talked about that last week. Oh good. So, so it's done we we had to prepare for the 1.23. So, I'm not even sure that we really need to talk about that today. So, no I think everything done is self explanatory. Excellent. Okay. Any specific items on the work in progress that you'd like to highlight so I've got one I can. I can talk to this one I've not yet done the system 390 upgrade. So we don't have a system 390 agent yet on ci.jankins.io. It's not a big task. I just been busy with other things. I can't not have any negative impact on any actual tasks that that ci.jankins.io does so it's it's a harmless thing. It just, we like to have the agent available so that we can use it for integration tests and automation. I can talk about the the the one below about the immigration. We are starting to work on the puppet side of it with the mounting of the LVM volumes and dealing with that and this is bringing us to the puppet problem of updating a gem for LVM and deleting the agent on some of of the machine. So I think it's mixing with other. Good side project in that in that milestone. Okay. And this. It's great that I'm I've been managing infrastructure as one offs puppet is automation that's much much better. Great. Thank you. And I think it's it's a little on the side of a puppet upgrade campaign to later six dot x. We write because this this is a highlight that there are. We're running an older version of of six. Yeah. Yeah, before before dealing with this one we need to apply all the update of the LVM gem file and check every agent to make sure we're ready to go through is this one so this one will have to go on the next milestone. Which makes makes sense. Good. All right. Let me change that. Yeah, go ahead. I will take care of moving. The not finished. Task to the next milestone. Okay. And then we've got a table here of new items. So I have not looked at these are the there are any of these that we need to highlight here for the group. I'm sorry. I don't as I as I scan through these I don't see any major items that I think would be a risk. We certainly want buildings. Now. Yes we can everybody go ahead. So the new important issues. We don't hear you anymore. So everybody sorry we lost you again. He put some message on the discussion. Okay repository. Okay, so can okay. Just keep the dawn for it can happen to me it's almost done explanation in the pair on that other repo. Ah, good. Okay. Ah, yes, so he was advising skip the done. Okay. Good. Thank you. Yeah, I was just looking are there any things in this that are potentially hot or important. And for instance this weekly really spilled does not resume that one's a general problem tied to pipeline sometimes not resuming. And so that's being worked on and the Jenkins Jenkins plugin level not something that infrastructure. Yeah, I this key cloak when worries me, but I assume it's been open. It's been open for a while so it's not clear. On that part, I think that they just did something with data dog to check if the process of login is working so I think he just had a data test that use specific user for data dog. So I'm going to login the key clock and do the full login path to check if the key clock is responding. So I think it's brand new it just did that. Great. Okay, so that's, that's, and that's, so it's awesome. That was terraform. Okay. And this migrate blue ocean remaining jobs that one seems like it could be a major effort. Just because this is a these are jobs that previously I think we did not manage. So, okay, but Dami and it's looks like is working with Olivia Lami on it. Any, any other topics we should review here today. All right, then I suggest let's call ourselves done for today I'll stop the recording. Thanks very much. Thank you.