 Recording has started. Hello everyone, welcome to the weekly infrastructure meeting team. So for the 8th of August, 2021. So let's start by announcements. So we have been able to release Jenkins 2.306. So congratulations to everyone involved in that weekly release. The checklist is complete. Mark, you might have a word about the docker image and that topic. Oh, yes. So the Docker image definitions add some new tags. Previously, the tags were latest slim Alpine. Now there are additional tags. Latest dash JDK eight slim dash JDK eight. Alpine dash JDK eight. It's a bit redundant at the moment because JDK eight is what's currently delivered in latest and in slim and in Alpine. But beginning with next week's release, our intention is to switch at 2.307. So that latest will become JDK 11. And slim will become JDK 11 and people who need JDK eight will use latest dash JDK eight. Thanks Mark. It's a great job everyone. So the activity is quite was quite slow this week and in a coming week. It's a middle of the summer. So let's start. It's been a numerous time that team. Yeah, come was unable to, to join us. So it sounds like that the time of the meeting is not the best time for the team. So the idea is to create a poll. To find a new meeting time that will allow team and every usual contributor and attendees to, to see the meeting. Mark, do we have a poll we use poll tool that we use to walk, maybe this course could work. I usually use doodle, but a poll with I hadn't considered using discourse. I don't know how to use discourse for a meeting time poll, but that's a good idea. So let's try this course to see if we are able to do that. So gave in, if you see that recording, we, we're going to ping you on for some help, maybe on IRC, but I think this course might have some kind of plugin like this one. Otherwise let's switch to the third. Good. Good suggestion. Okay. Okay. So Mark, you're taking the action. Cool. Is there anything else about the topic for new meeting time? That's it for me. Nice. On my side, I'm working on CI Jenkins IO. So work in progress for ACI and Kubernetes. So the goal is to still to move some workload. I did not work a lot on that part right now. I was more focusing on the puppet. Puppet code. So I took some trainings to master a bit. The reason is the second point is because I will want to implement as soon as possible an automatic updates of the agent template. So right now it's doable quite easily with updates. I for the Azure templates. However, for the MEI, there might be some work to be done there. So I need a bunch of updates, CLI contribution and the puppet code. So I was working on that part experimenting. We discussed with Olivier before his holidays that still the ACI to Kubernetes should be the priority. So I'm going to resume that work starting from tomorrow. And I also took not a lot of time, but I started to study the changes between Terraform 0.13, which is the version we're using currently, and the version 1.0 that will fix the syntax of a Terraform state, the syntax used, et cetera, because it will be a LTS release. Right now I've worked on the AWS as a test, but I've been blocked and I stopped at that part. I realized that before going to 1.0, I need to update all the Terraform module we are using. So that's work in progress. And once we have the latest version, then I should be able to switch to Terraform 1.0. The reason of that change as a reminder, it's because we'll have to start resources on Digital Ocean on Scaleway, our new sponsors. And also eventually on Oracle Cloud as well, because it works with Terraform. So the goal is to have an unified and long-term support for managing infrastructure as code there. Is there any question on CI Jenkins, Terraform? So the progress on ci.jenkins.io is tied right now to Puppet and getting automation there. And the concept is still that I'll be able to continue using labels to describe and we will have Kubernetes agents that provide the same labels and limit the amount of the number of them that they allocate. So we'll be able to watch those agents, see that they're healthy, et cetera. Exactly. Initially, I wanted to work with Tim on that topic because he saw some build of the BOM that are quite complex builds. The thing is that we are too asynchronous these days. So I'm going to start by switching all the CI Jenkins.io job for Jenkins Puppet code. That one is using the ACI containers with the Ruby agents. I think we are almost the same to use this. So I'm going to switch that project fully to the new one. So I started to work because it's using a shared library. So I need to find everything to create a temporary pipeline for that. But that will be the first iteration, ensuring that that project can work as it. And once I have the template for Kubernetes, I will be able to create a bunch of others. Great. Thank you. Thanks very much, Damien. And finally, so that's the topic on you, Mark, preparing the Docker image. Yeah. So as a reminder, next week's 2.307 release will switch the Docker image. And then one week later, we'll switch the Docker image for the LTS. So and the intent also is to switch the agent images next week. It probably won't be next Tuesday because next Tuesday will be dominated by delivery of the weekly. But think Wednesday or Thursday, agent images will switch. That means between that switch and the release of the next LTS. Some users will be switching to run that their agents will run with JDK 8 rather than with JDK 11. As the hosted or as the Java version running that agent. So. Agent. Agent image changes in addition to the controller image. That's all that I needed to share there, Damien. Sorry, I was speaking completely muted. So that's that's all for me. I don't have an other topic. Do you have a topic on your side? None, none for me. I'll go decode how we do the. The poll with discourse. I've never done a discourse calendar poll before and we'll, we'll see what we learn. Cool. So that's all for today. So let's see by default in one week, unless we already have a result for the poll. But by default, let's see at least next week for the next meeting point. Right. See you next week. Bye bye.