 Hello and welcome. This is the Jenkins platform SIG meeting for February the 28th of 2023. Today we have Mark Wait and Kevin Martins and of course myself. We still have a few open-action items. I think we won't get rid of them shortly. And it's of course about Docker images for the Blue Ocean container which are deprecated. We haven't announced yet the deprecation of the image or have we Mark? I don't think we have. No, no, we have not. It's been discussed here. I think the deprecation of this image would be best done by adding the administrative monitor that's mentioned in a later action item or in a later topic. And then we announced the deprecation, blog it and people see it in their Jenkins Weekly. Oh, hey, this thing is deprecated. Yeah, because we still see from time to time people coming out of the blue. What? Wait, deprecated? Really? Yes. Right. And we need a way to at least point them to, hey, your user interface was trying to tell you this. You suppressed it because they may, but at least we attempted to tell you that this thing is deprecated. Okay. And speaking of things that we want to get rid of, we used to love the Blue Ocean and things that we don't love that much. Like CentOS 7. We like to get rid of the CentOS 7 Jenkins Contra Docker image. As you may already know, we've thought that in the previous meetings. Officially, CentOS 7 is still in maintenance update from 2020 until June from next year, so 2024. And we want to deprecate the CentOS images for Jenkins. And we definitely want to get rid of that. I know Mark, it's one of your motto, get rid of CentOS 7 for various reasons. One of the reasons I have it that it's really difficult to keep it up to date with a recent version of Git. For example, I know how much you love and use Git. And that's a pity that for CentOS 7 it's really, really hard to get a recent version. Unless you compile it by yourself and help. So in previous meetings we talked about maybe needing a JEP about using an administrative monitor. So if I'm not mistaken that the kind of thing you see when you have a deprecated plugin and when you have a new version of Jenkins and all of that appears in your Jenkins controller. Am I right, Mark? Yeah, and I think we may actually be able to do this with just one JEP and a pull request to Jenkins core now that I, I look at this a little more think thank you for writing thank you for the notes. I think that Jenkins enhancement proposal that we need is to change our usual behavior our usual behavior would be CentOS 7 end of life is June of 2024 when the CentOS project ends its life. We want to end support of CentOS 7 sooner say September of 2023 October some arbitrary date we choose. That is a change for the Jenkins project and so the JEP is to propose an acceleration of the end of life for CentOS 7. With an administrative monitor I think we can just do it as a pull request proposing now the pull request will certainly get lots of feedback, lots of comments from people about hey, either this is not general purpose enough or it's to general purpose. What are you thinking about doing it this way why not do it this other way, and, and those those conversations will be valuable and useful and important and will give us a better solution. Because it's, this is sort of an administrative monitor for deprecation of a thing that deprecation of a thing there could be multiple deprecated things and we need a way to represent multiple deprecated things, portably cleanly extensively, etc. And so that's that it'll actually be a fun thing to add to Jenkins core. And certainly there will be lots of conversation I expect lots of conversation and some really good insights from the high skills people around the organization, not me, who know how to do Jenkins core development really well. They'll suggest, we should do this instead of that and we'll get a much better solution as a result, because we know we need to deprecate blue ocean Docker container right the blue ocean container image. We know we, we, we should tell people that Ubuntu 18 is end of life as of April of 2023. And likewise our Alpine container images. I think in May of 2023, the oldest of those container images will be deprecated three dot 14 if I remember right is one that's deprecated so. All sorts of places where this technique may help users and where we need the technique as a way to make things very visible that hey you're running on so as a as a very specific example. I saw posting today on community dot Jenkins.io from a user who said, I have a Jenkins that's running on Ubuntu 16 04. And my answer to that is, that is absolutely crazy because the Jenkins project does not support Ubuntu 16 04. And we don't support it because the vendor does not support it right canonical does not support 16 04. 1804 is the oldest they support and that will end support in May of 2023 I believe or April of 2023 so. So, we could do them a service by saying, you are running on a platform we don't support. Oh yes indeed yes you're right and they may, they may be unsettled by that they may find that very aggravating what you're telling me, but but it's the truth right the Jenkins project does not test or support or in any way do any work on Ubuntu 16 04 and and we won't. Yes, and as you said that could lead to good conversations between people in the community. And I guess people from the security will chime in say, what you're going, you're going to deprecate all pine line looks whatever what about getting totally rid of all the pine images and so on. Why not. But yes, I hope that people will discuss and find the consensus afterwards. It's very interesting and you're right that would be very helpful for the end users seeing that they are running their Jenkins on an underwater system by Jenkins and by the vendor itself. It's super cool. I would love that. And by the way thanks a lot for the link you gave us few meetings ago, maybe it wasn't docs office or whatever. I'm going to deprecation the end of life the open source website. And yeah, today I saw a tweet from a French guy saying, oh I found a nice website to manage my end of life and say, I know of a better website which is open source, because the website he used to use didn't list Jenkins for example. So yours is better, whatever. Kevin Mark any other informational question whatever regarding that subject. No, we just I think for right now we're in the talk phase, rather than the implementation phase and I suspect will will be stuck in the talk phase for several more meetings just because I don't have capacity to do and I don't know of anybody else who has capacity to do it. But the concept feels like the right concept and let's let's keep working on it. Yeah, to me at least looks pretty cool. So without further ado, let's go to the next subject, which is the latest updates on the agent images, nothing disruptive. This time, just a few things about get once again, because I think there was a CV you recently about get so the latest images now have the right get version until the next CV, I mean, I suppose, and the inbound agent got an update of the parent image to update in fact, the three and then the four. That's all that they and for the update cli we don't care because it's something that happens behind the curtains, and that doesn't change anything when you are using the input agent so something totally optional but we still have a few minutes. So I discovered by accident yesterday that the Android build tools are now natively compatible with art 64. And guess what it has been a long time I never know I was stuck for whatever reason with the version 30. Something and so it never worked for our 64 unless you know for example lots of people have now arm and one with an R64 controller and building Android application with Jenkins all these machines. You had to use the Rosetta, which transform the xx t64 instructions into our 64. And this is not perfect. You just have to switch to Android build tools 31.0.0 and bound. It just works. That's typical for me because I build Android apps with Jenkins on a regular basis but on xx t6 machine. Yesterday night I tried something on those small R64 machine and it worked. It was amazing. Previously you had to do some hacks with some binaries taken from a Chromebook for example to get it to work so now as a developer. I'm super happy that it does work. And yeah, another subject about Jenkins. I know every meeting I talked about race five, which is a very promising CPU architecture. And I was pretty proud of myself because I had made some tests with some very agey open JDK bills and so on. I thought I was really a pioneer, you know, and unfortunately I tried a chat GPT today for the very first time. I didn't want to experiment with that but I asked chat GPT, do you know about Jenkins, of course. Do you know about risk five, of course, do you know about risk five and Jenkins and then he gave me some pointers of blog post and ready thread and GitHub issue. And I thought end of 2022 was the beginning of Jenkins on the risk five, but I was wrong. So wrong. Some people experimented in 2020. So yeah, I'm not a pioneer anymore. So I'm happy and sad at the same time. So with any of you have any other things to add before we close the meeting. I do not. Thanks very much for your time. Thanks. Thanks a lot for coming. The video should be up on YouTube in 24 to 48 hours and we'll see each other 15 days from now. Have a good rest of the day. Bye bye.