This is it right here. It's a brand new feather. It's so sad. Let's show the feather. You see how there's, shh, it is still bleeding. This is bleeding. It had blood, so that needs to come out right away. Ready? Oh my fellow Snippers, flighters and newbies, welcome to my channel. My name is Marlene McCohen. We are about to do something very important today. For those of you who just watched my video on Leo not too long ago with his blood feather. See how a blood feather? Oh God. Oh wow, look at that. I know a lot of you guys found that helpful. So I just want to give you a heads up on what's about to happen today while we're up here alone. Caroline's Hyacinth McCohen Glory has a blood feather. It's very large. She called me. She said, should I take him to the vet or can you help me? Obviously we can help her, but I want to say something to you guys before we do this. I thought it would be a good idea for us to film this because I think you could get a lot out of it being as Gloria is a different kind of bird. However, I just want to let you know if you guys put any hate comments towards Caroline at all, I'm going to delete them and I'll tell you why because she reads them and she's a person too. So as much as you might feel something about her, if you write something negative, you are bullying and you are transferring that negative energy on somebody and she feels it. So she almost was like maybe I just shouldn't be on your channel. Maybe I shouldn't film this, but she's doing it for the love of the bird. And on that note, it's not that she couldn't take it out herself. It's that a lot of times you need more than one person to do it. I prefer to have Jenna with me.  You saw George helped me do Leo and in this case with such a large bird, the more people we have the better. Just so you guys know, obviously she could do it herself, but she prefers to take the safe route and have some help. Hi guys. So here we go. Oh baby. Yeah, so it's the left wing. Okay. And it's one of her primes. It's not the first set. It's the second. Okay. Primes. And she was just bleeding and I don't know from where I think she chewed it off. And we got here as soon as possible. Okay. So just so you guys know what we have ready as I asked her to bring a blanket. So we have a blanket. We have a towel. It's a real soft blanket to wrap the bird up in. I think we're going to do it over. Can we do it over here, George? Let me get the powder. It's happening. It's okay baby. Right here. It's a brand new feather. It's so sad. Let's show the feather. You see how there's, it is still bleeding. It had blood. So that needs to come out right away. Ready? Ready? One, two, three. Wow. Thank you so much. Okay. Don't overdo the powder and we'll put some pressure on it. Where is it? Where is it? Where is it? It's all right. Just put it on. Thank you guys so much. Thank you. Thank you. Like a mommy with her baby. That was a big feather. Right. It is. It made a mess. Make sure you find the point to put pressure on. Her heart is beating. Let's check it. So guys, here's another example. See the blood coming out? If you don't pull that out, it continues to bleed. Wow. Look at this feather. It was bleeding right here. You see it broke right here? That's a dangerous spot. Yeah. That means it like. But look at how big the shaft is. The shaft? Yeah. It's like humongous. Oh poor thing. What happened? I say just to let you make sure to get her taken care of. Thank you so much. You're welcome. Oh ow. Can't do that. I forgot I had her on my shoulder. I've done my lesson with those things. Leo is so obsessed with little kids that George came out and wanted to say hi and give Leo a hug and he got bit by Leo. I feel like I just want to work and came back. But you're very welcome. Hug you from afar. Bye sweetie. I love you. Bye. Thank you so much, Marlene. You're very welcome. Wow.  I can keep it as a swimming. Let's check the blood here. Let's make sure that we have the right pressure on it, okay? Megan, get the present that we have for Carolyn. Do you have it? Yeah, I just got kind of packing. Is that how come it's so big? I told you it's enormous. This is a large bird box. Oh my God, it's so big. We have a present for you, Carolyn. No way. I got a feather box. Yeah. Thank you so much. Why? Because you don't have to. But we wanted to give you one as an influencer to see if you would do an unboxing on your channel. Oh, gotcha. What was all that screaming you were doing in the room just now? Oh, so for this month's feathered front box, we have charms.  I haven't seen them. Carolyn's going to pull it out. Carolyn will be the first to see it. Yes, I have a straw in my hair guys because like when I don't have stuff to tie my hair up with, I grab anything. Kind of matches my outfit and jewelry because I was wearing a red snipper shirt today. Go ahead, Carolyn. Be surprised by the box and let me know which birds you think will like it. Come do it in the light so we look beautiful. Carolyn has all sizes of birds. Our large box is really for medium birds as far as African grays, some cockatoos, galak cockatoos. She has some very large birds. One day we'll make a large box for the larger birds, but if you think about it, there ought to be like four sizes. So like extra small birds like the budgies and such, small birds like Senegal's, Conyers, Cockatiels, then technically the medium slash large birds, which are large birds like Jersey and Leo and such. And then later we'll make a bigger box. So she has some all different sized birds. So these toys will work if not obviously for the macaws. They'll work for her other birds. Okay, I'm excited to see what your reaction is going to be. That it's kind of like Gucci. I don't even want to break the sticker. I know. Wow, Glowy, tin cone. Can have some ice cream. Glowy likes it. She does. You want it? It's fine, she likes it. Okay, I do like it. Oh, this is good. It's kind of like, you know, like if you have kids, the kids will like you on it. It's a sign she loves me. Okay, you can play with that. I open the trunk. I didn't even do my nails. Oh my gosh, this is like so small. This is the smallest birdie I've ever seen in my whole life. Oh my God. The tiniest bird in my life and the biggest bird. Do you know who that bird is? He looks like a cockatiel of little like... It is. That was my first bird. That's my first bird Dooley. Isn't that exciting? So for Thanksgiving, we did a thankful box to my first bird. Aw, how sweet. Isn't that cute? My first bird was a budgie and then it was a cockatiel and yellow cockatiel as well. Her name was Purdy. I'm gonna keep this trunk. What else is in the box? So next toy in here is this nice big wood toy. Don't hit me with it. No, little stickers. One for magnet. For the refrigerator. And that's also the little cockatiel, right? I have to kiss Marlene. She gave this to us.  Do you want one of that? Oh, that she likes. That's what she likes.  Those are hard blocks too. They're nice. They're nice little blocks. She likes the blocks. And then I think I'll put this nice box into Angel's case. I was gonna ask you if you would do that. Make Angel a house with it. Yeah. Is that Angel's new house? I love Angel's though. Will you send me a picture of it? I need to open up a little hole right here.  We'll accept, we'll accept a hole in our box for Angel to live in it. He's gonna like make the hole bigger and he was gonna work his way inside. He loves, he has houses. He loves houses. And he loves all these stuff. Angel, my little oracle. Thank you so much. I'm so glad you liked it. But look though, these toys are pretty good for the big board. This will last for sure. We're really proud of this box, honestly. It's beautiful. Just so much fun putting it together. If you guys, maybe I'll give you guys a tour of the room. Not today. Put everything back in. Not today. It was a good choice to come here instead of the bit. Josh did a wonderful job. Okay guys, so Carolyn had already put this in the car, but I wanted to take another moment to give you guys an extremely good look. If you don't see this little bulb at the end, see that bulb right there? So if you guys didn't see that bulb at the end, then you have not gotten the complete feather out. Generally, you should see this entire shaft. I'm not sure if I had mentioned in the last video, but what you want to put on it, if you have quick stop, quick stop has a tiny bit of medicated to basically prevent the bird from feeling pain, but you can also use baking soda. That is actually what I use so that, you know, and then you apply pressure and stop. And I think I didn't mention that in the last video.  Once you pull this out, this will close. Once this closes, it should essentially stop bleeding. There are some extreme situations where if you can't get it to stop bleeding, but you should be able to with enough pressure usually. I believe that's in the handling, but sometimes in an extreme case, let's say the bird just never stops bleeding and never stops bleeding. Then what they do at the vet, they cauterize it. Basically, they apply a heat with metal to close it. Don't ever do that to your bird. That's just something that the vet is prepared for. I've never had to do that. Usually what you guys could do also, if you are having trouble with the pressure and stopping the bleeding, you can put a natural mask on it, like a clay mask that'll close it right up. The goal is to not let the blood come out of the bird's body anymore. So that's the goal right there. So a clay mask can work really well in extreme conditions. And some people actually kind of apply like soap, if you know what I mean. Like they put their birds feather through a little bit of soap just to put that clot in there. But the first thing I would always do is the baking soda. You don't need to apply so much. George just picks to cover his bases, I guess. All right, guys. Don't forget to subscribe to Carolyn's channel. I love you guys so, so much. You'll see lots of fun flight videos and drama videos on her channel, which are always so fun and entertaining. And we are not a bird channel. We are a drama channel. That's what she's decided. And I think it makes sense. I love you guys so much. Bye. By the way, don't forget, if you guys are looking for an amazing bird food brand for your bird that is healthy, organic, and not full of food colorings and sugar and peanut smash, check out Marlene's signature blend. I did this along with Top's parrot food. We've just launched in the UK. Northern Parrots now sells our food. You guys have been asking for it. You got it. Also, Things for Wings in Canada sells our bird food right now. I'm proud to announce and they will ship it to you. I encourage you guys to check out my feathered fun box. It's a passion project. It's a subscription box that comes with parrot toys for your bird and also special merch. Kind of like my dream box. Honestly, I put so much into it. I love that there's something like this for birds out in the world. That's why I created it. www.featheredfunbox.com. I love you guys so, so much. Thank you for listening.


Welcome everyone, this is Jenkins Platform's SIG meeting, we're on the last day of January 2023. Today we have Mark, Wade, Kevin Mardens, Damien DuPortal and myself, Bruno Verashtel. We have a few open-action items in the agenda, the first one has been done, thanks a lot Mark. We had to find a better time for this meeting, which used to be on the Friday night, for us, European folks. And on Tuesday night, it's not even night, it's very beginning of evening, it's much, much better. So, I'm fine with us, thanks a lot, and it won't change, only if somebody asked to change it. So for the timing, the time we chose is perfectly perfect. Now, Damien, you're there, we have a few items for you. It was in the open-action item, I think we can get rid of it, but I just want to be sure. We had to talk about the platform support container, Windows 2019, Windows 2022. If that's done, Subject, can we remove it? Infrastructure area, it's done, we can execute Windows 2022 container, it's supported. But it's not done for the Docker image, we don't have a pull request. We have a pull request from a user that's never answered, so I consider that pull request being dead. So someone need to work on adding the new Windows support. However, before that, so for the agent, we can start working now, anyone interested can get started. For the support of Jenkins Core on Windows 2022, for that image, let me try to read it correctly. We should not spend time on this one, because we know that we have a publication issue with the Windows image. Jenkins Core hasn't been published properly since months. We have a user that is trying to help, that user is lacking information I try to give them, but it's not that easy. And we have an overall publication concern that image, so that will not make sense to start working on 2022, because we are not even sure if we will continue shipping these images. So I propose to put that on hold and remove the topic item on platform SIG for now, or put it on the backlog. I like that. I think we seriously should ask ourselves if we want to publish a Windows container image given that result. A Windows container image for Core. Agents agreed. Agent images, it makes everybody sense we're actively using them. But Core as a container image for Windows, question well how useful it is to the community. No idea. I'm using WSL. I guess lots of people use WSL when they are using Windows. I don't know about why and when somebody should use Docker for Windows on Windows. I don't know. If it exists, there is a reason for that. Certainly there is a reason. As an agent, it works very, very well. Or, okay, maybe that's too strong. As an agent, it works reasonably. And it's a little bit cheaper than spinning up a new Windows virtual machine, right? You've already got the machine running, you just take a container and run it. But why not a Linux one? Because I need to do Windows stuff. Oh, of course. Some people do. I know, I know, I know. It's hard to imagine there are those of us who actually run on Windows every day and who use Windows all the time. Okay. It's not Friday, you cannot troll anymore. We changed the day, you cannot say... Okay, it was even not a troll. It was a troll for me, I couldn't imagine. Yes, some people work on Windows and they don't have to, they choose to. And you're right. .NET is not a big one for us. But there are certainly community places in the Jenkins development environment where it is a big deal. And .NET on Windows is much better than .NET on Linux, right? The .NET on Linux port is a subset. Yeah, and I've seen some messages in the community discourse from people which are building for Windows with documents.  All sorts of dark things with Windows that are very Windows-specific, yes. And that, yes, exactly. Sorry about the troll, I couldn't have myself. Or update CLI to run an end-to-end testing with the Windows binary. We generate it on Linux, but we want an end-to-end testing to be sure that at least we smoke this thing. I know those terms. Okay. Thank you. Next, Damien, it's on you, this one, too. We talked a long time ago about the Docker image download statistics. I guess you've been so busy with JetFrog and so on that that's not the main subject you're working on. So it's still a thing. Should we have a look? Should we remove it from the open-action items? Yeah, so officially, yes, I have been busy. Officiously, not officially, I forget about that. To be quite honest, I'm sorry. I don't think it should be, I propose to move it to the backlog because it will be useful. But given that we added the new Ruby 9 image that we are speaking about Windows 2022, it means that we are not choosing metrics as a way to decide if we should or should not. It's not the main decision lever. It could help. It could be the main decision lever, but right now I don't see any urge of doing that. So I propose to move that to backlog, but not delete that absolutely because it could be useful. I'm not the only admin, so I need to check with admin, but I think there will be other people who could access that or better. I could create accounts if it's okay with only the ability to read these statistics. As far as I can tell, with the plan we have, we might be able to have accounts with only this permission. So people who won't be able to write or push images only get the statistics. Okay, and as we have two members of the community which were found of statistics, Jean-Marc Messain, Adrien Le Charpentier, maybe they could use that account. Absolutely. Thank you. Now, another big and long subject. Merging the Docker agent repositories into a single one. I don't know if anything has progressed with that subject. Not yet. Should it still be an open-action item or do you want it to be in the back? Yes. For me it's a top priority item for the platform SIG. Cool. Thank you. Now, the Docker image is the one for Blue Ocean. We've been talking about this one for a few meetings. Is there anything new, Marc, or Kevin, or Damien regarding this image? Are some people still talking about that or just maybe everybody forgot about it? It's not that I've forgotten about it. It's that it's not been nearly close enough for me to do any work on it. We do just need to announce its deprecation. Go ahead. Sorry, I meant end users, not people which were supposed to work on that. No, just people asking for some help or some news or anything. I've not seen any further requests in a month or more, not on community.jankens.io, but of course, if they ask on community.jankens.io, Gavin Mogan very promptly tells them, just like we do, that that container image is deprecated. So he's carrying the message very nicely. We just need to make it official. Yeah, thank you. So should we keep it in the open action items or move it like a cycle log? Let's keep it on the action items because there's benefit to us to get rid of that. Definitely. But later on in the document is written, you have to talk about that each and every meeting. So we do that. Okay, yeah, just there. Got it. Thank you, Mark. Now, contrary, it's still in the open action items so we can get rid of that. And thanks for Windows. We also talked about that. So yeah, it will go into the backlog. If you don't mind. Butchering the document. Now, ongoing work with Docker images. So I've seen quite a few changing these latest Docker agents. But we also have new platforms. It was from the last meeting, I guess. So maybe we could get rid of that now. We know that we have Windows 2022 available thanks to Stefan for the infra. Yeah, I would actually phrase this one is, for me, this was container images. And so for Windows 2022, we don't have it. But you could say if UBI 9, we do have. There is clearly a new platform, UBI 9. How do you call it? Do we write it? Yeah, that's great. No, UBI and then the digit 9. No, no, no, no. Yeah, sorry about that. Exactly. With JDK 17. Maintained by Oliver Gonja of Red Hat. Okay, call for a TSM, but got it. So real old. Sorry. G-O-N-D-Z-A. G-O-N-D-Z-A. The J, the Ilung. The later. That one needs to be a exact, perfect. Spell to the exact. I can go get help. A-B-C-D-E. I get it. Yeah. Right. He is also the maintainer of the UBI 8 container image. So it's a good fit. Got it. Daniel, is Wolfi still a subject? Or are we still thinking about that? I wasn't present when the topic was raised on the platform. I'm sorry for that. I think that will be worth walking with that or asking the person that with Chen Gardeuve, who built a preliminary example of Chen Ginseng and Jankins agent. That will make sense. The reason is that this specific definition will help people who want to run Jankins without taking many risks. So it's not for people that require Sun2S for the container image for whatever administrative reason. It's for people who really want to rely on something that should be only as small as possible and as secure as possible. For people like me who don't know much about Wolfi, could you tell us in a few words what it's all about? So the idea of Wolfi is saying, when you provide a container, having multiple operating systems not only is a nightmare, but also is a risk. Because most of the time, what you add on the container, you can control if there is a CVE or a security issue.  However, the dependencies that come from the upstream image are risky. Right now, if you run a security scan on the latest Jankins image, even the one we just published, you will have a bunch of CVE or security adversaries and tools that we don't even use because they are part of the default Linux distribution behind. The idea with Wolfi is that you only install, build and run what you need. So for Jankins, you only need a GDK. You only need a Ventually Curl for running the script shell supports at the beginning of the image. But you'd only need a set of tools that you can exhaustively define. It's in the area of the new S-BOM trend. I say trend in a neutral way. The S-BOM is a field of material is to list what is exactly inside the image that also help on the area of build reproductability if you want something to be rebuilt. Because each time you run an apetite get package or apk add, you can create mayhem in the dependency chain. So Wolfi is an operating system that has been built only for running inside containers. It's not aimed at running machines. And within container it reused part of the Alpine apk package system, but also it work a bit like Nix. You compile and build each of the tools you need and you create your own dependencies. So, would it be, sorry to interrupt. Would it be a good comparison or totally bad one talking about the old Linux from scratch that we experienced with years ago, but just for containers with a very small subset of tools you need. That's the same idea, but only containers you said and with tools that normal human can use to extend the image if they want. Thanks a lot for the explanation that was crystal clear. Oh, if you ever have finished with that. I haven't done it yet. No, that's okay. So, just to know chain guards people, I assume some former Jenkins and Jenkins 6 contributors, they have built, let's say, test images of a Jenkins score using GDK17. I think it's the T-Marine GDK17, but not sure, where the amount of security advisory from the chain guard security scanner has drastically decreased. Like you have one or two instead of hundreds. Like drastically. Okay. Oh, that makes more sense. I don't... Please be with me. I'm not saying we have security issues with Jenkins image. I'd say the scanner points a list of potential security issues that can or cannot be exploited. They don't give you actionable on what to do with this. Yeah, which are part of the latest Debian, the latest Ubuntu, the latest Alpine and so on. They are there. Absolutely. Cool. Oh, thank you. That's interesting, really.  I'm just... My skepticism kicks in here because of past experience with Linux from scratch kind of experiences, right? Linux from scratch and its variants, the free VSD package system, the open VSD package system, those things are notoriously challenging to maintain and make portable. They take a lot of work. And Wolfi is a young project, right? I mean, free VSD's package system is a very mature project. Arch Linux is a very mature system. Wolfi is, for me, still brand new. And I'm hesitant to jump on to it yet. Yeah. The thing is, I really think we need, if we want to be cloud friendly, to go in that direction because Wolfi is clearly a way to have some exposure, to validate some behaviors of Jenkins, to clean up the list of dependencies we need on the Docker image. We will clearly benefit from trying to fit Jenkins into Wolfi. We will learn from that and we will improve all the other images by saying, oh, we need that dependency. And I've got a real-life example today, Git. Which version of Git is installed on the latest GDK 11 image of Jenkins? 0.30 something? No, it depends which is the base operating system for the container. For Debian, it's one version. For UBI 9, it's another version. For UBI 8, it's another version. For CentOS 7, it's a terrible, awful, evil version. Of course it's CentOS. It's CentOS 7. So yes, Damien's point is correct. If we take responsibility to deliver the version of Git we prefer, we would switch and always deliver the most recent release. We would be delivering Git 2.39 and not care about the operating system vendor. And that's what Wolfi, and I agree, that's Linux from scratch and Wolfi both give you that benefit. You get to choose. I want Git and I want it from the latest release. Yeah, the thing is I don't think as much as you do, Mark. I don't have that much experience either. As soon as I see something in you, oh, look, a squirrel. That's the way I'm interacting with Wolfi. I got a proposal here because we are all busy and that kind of thing should not rely on the four of us. I think we should ask people at ChainGuard and tell them if it's okay and if there is no objection. But my proposal is we ask them that we are okay to introduce a new image. And so if they are willing to open a pull request on the repository, we can get started and spend time on reviewing and understanding it. The way I see it is that we know what we don't know. So if they open a full request, we can then start the discussion on, oh, how can we document to end users? Hey, I got, I'm a could use Wolfi image. If I want to add the AWS command line inside that controller image so that Jenkins can do whatever with that, with the controller level or Kubernetes, some plugins requires that or would help. What would be the path? What is the documentation on Wolfi that helps me to install or build myself AWS dependency so I can build it? That's an example out of the world. But the goal is that we can focus on that part as reviewers and maintainers while people who already have the experience on Wolfi could get the heavy lifting. They already did it so they could provide things and we just have to package and polish that and get started with that first iteration. What do you think? What do you mean? Sounds very reasonable to me. Is there someone volunteering to contact them or should I do it? Because I volunteer as a foldback because I'm interested, but I don't want to step on someone else too. So if you want to contact them, I don't mind either. I'd love to have you do it rather than me because my biases lead me away from it. I think your interest leads you towards it and that's a good thing. So you see it as a positive and I like that. I'll change that into David. Oh, you can keep working for whatever reason. Sorry. Okay, thank you. Why are we talking about new platforms? Can we talk about Arc Linux? I know it's linked to the statistics we don't have yet about the usage of the different images, but is it still a subject should we duplicate Arc Linux or not without having the numbers of the loaded images? I think we should. But again, my bias is to remove things that I am not persuaded are of value. I also think we should start announcing the end of life of the CentOS 7 image. But again, you're hearing my biases being echoed loudly here. Yes, I was saying it would be perfect where there is nothing more to remove from. So maybe removing Arc Linux will make Jenkins containers just a little bit more perfect. I don't know. Okay, Damian, Kevin. Okay, I don't think it's worth it's deprecating. It's right now we have at least one person using the base image. Ooh, okay. Nice. Last time, if that's okay for everyone, we'll move on. We talked about Mark, talked about the Debian 12, which is a bookworm that will not deliver OpenJDK 11. I don't know if there's anything new. And by the way, I thought I knew a few things about Debian, but I learned this morning that all the name of the distributions were linked to, what was it, comics? Story story. Story story. Yeah, I didn't know that. And that's why Unstable is seed, which happens to be the bad boy at the neighbor of... Anyhow, I didn't know that. Now I know and I maybe will quit using seed. Okay. It was from Veronica Explains, which is a YouTube channel I happen to watch from time to time. Anyhow, Mark, any news about that? Yes, so further more details. I've learned more since having further discussion and looking at end-of-life dates for OpenJDK 11. So end-of-life date for OpenJDK 11 does not happen until at least 2027 or 2026. So it's got a nice long life ahead of us. So there is not an urgent press that we need to drop JDK 11 support for Jenkins. But I still think we are doing the correct thing to say that in April or May, whenever they release Debian 12, we will change the Jenkins documentation for Debian and for Red Hat to describe how to install with Java 17. It's fully supported. It's already fully supported. And there's no reason we should describe Java 11 when Java 17 works so well. I got a question. When you say OpenJDK 11, are you referring specifically to Timurine Distribution or the Distribution package by Debian when you have to get installed OpenJDK? So when you do an apt-get install of OpenJDK, the package provided by Debian, the Debian project will not deliver OpenJDK 11 because I assume it's because they don't want to have the life, have it live longer than they have to support it beyond the end of its life or their operating system. Okay, because the thing is that we don't use that package today. Well, careful. Our installation instructions on Jenkins.io, you use that. As does our package install instructions for the dev package. Now, you're right. Container images don't use that. And we highly recommend container images, but for those who are using native package installers, we do continue to use the operating system packages, both for Red Hat, for Suzy, and for Debian and Ubuntu. Yeah, and on smaller machines where having a Docker container is slightly overhead that I can't use, I have to use the ones with packages which are provided by Debian or Ubuntu. By the way, is a PPA for Debian and Ubuntu the same for the OpenJDK build or not? I've never tried to use a PPA, so it's not a PPA, it's actually the OpenJDK. The OpenJDK package is actually provided by the Debian operating system, so it's not a separate thing that I have to do anything to enable. It's built by the Debian maintainers and validated by them, especially the leakers. Validated by them and maintained by them, and sometimes that was a detriment actually. There was a period five or seven years ago where they made a mistake in their maintenance of the JDK and that mistake caused some unexpected damage. Yeah, so it's actively maintained by the people on the Debian project. Okay, but this sometimes different depending on the platform of the CPU architecture, for example, I'm just thinking out loud about my RISC-5, which uses a zero VM from the Ubuntu operating system. And if I were to install that on another CPU architecture like R64, for example, it would be a hotspot enabled machine. So yeah, take care with what you are downloading from the operating system. It's not always the best JDK you could find for your system. Correct, right. But in this case, the benefit to our users, we're going to document Java 17, and we're going to recommend that they use Java 17 by documenting it. We will drop support for Java 11, and we'll continue supporting both. But there will come a time in the future when the Jenkins project will have a Jenkins enhancement proposal that will eventually drop support for Java 17. It's just not likely to happen any time during calendar 2023. We don't need to rush it. Of course. Thank you, Mark. By the way, will we one day or the other talk about Timurin because we're using it for our container images, but in the official documentation? Does it make sense not at all? Or do we have some kind of partnership, or do I know we have the list of the supported JDKs, but I don't know. Should we talk more about Timurin or not at all? That's a good question. Maybe let's bring it separately because you're right. We don't. I don't know of any place where we actively describe in the Jenkins documentation our intentional choice of Timurin as the container JDK, but it may be there and I just forgot. I think that's a good idea that we have made an intentional choice there to use Timurin and the choice was made actually I think in the platform SIG because Timurin provides the platform, supports all the platforms that matter to the Jenkins project. 64-bit ARM, 64-bit Intel, and System 390 are the three architectures that are actively supported by the Jenkins project. Our container images deliver at least some variant of each of those three. Thank you, Mark. Now, JDKs support for Jenkins require Java 11. Is that still a subject? No. Actually, I am proud to announce that the Jenkins enhancement proposal proposing to require Java 11 is now final, which means completed, done, merged, everything. So for Java 11, for require JDK 11 is final. So we have completed all the steps. Congrats on that, and thank you basically, I guess, for your input. Thanks very much to Basel, to so many others. Damian, once again, it's for you. Don't be mages. So you think that's still a thing? Yeah. Fixed. We found the issue. We migrated the deployment job on Trusted CI, and we were able to validate that the latest agents were picked, and we checked manually each job to see that there is no Git ball features from past years that were enabled. So we cleaned up that up, and that's okay. Three days ago. Wow. That's a major step. Okay. Now, JDK 19 available, that means on the infra. Am I right? Yes. Frick. Sure. Yeah. So it's done. Yeah. In infra, it's done. It can be used by people if you want to test. I don't see any use case for the platform because it's not an LTS version that should be the JDK 21. So I don't see any reason right now, but I might be missing use cases. Don't hesitate to add them. So that's why I propose to put that topic as done. Yeah.  That's a good idea. Oh, some news for the IBM S319X mark. Okay. Yeah. So, and that one has been merged. So I submitted that. I'll include a link and Bruno, you can just click the link to see it. It's a little more dramatic than I had intended for it to be, but click the link so everyone can see it in the recording. So the system 390 agent may restart one or more times Friday the 3rd of February from 4pm to 10pm eastern time in the United States. Got it. The red text, the issue is not resolved yet is accurate. It just, this is, I tried to choose the least severe of any of the options and apparently that still shows issue is not resolved yet rather than showing that the window starts this Friday. Okay. And the website is not that precise. No shame. It's a static website, right? Since it's a static website, it can't be time dependent. Oh, and you're all saying in the next sentence that state automation jobs are only known users. So even no human being will read what you just wrote on the website. Correct. I documented there as practice for that way people know if somebody were surprised. They could see it on status.jankens.io that the agent was restarted. Perfectly perfect. Thanks a lot Mark. Yes, we've seen some updates for Java in the containers. Am I right? So they're not just in containers on all the infra. These updates are deployed to all all Jenkins infra throughout all of our container images. Only one exception. Windows containers. Oh, okay. We have unchecked because when we deployed the rest, the official image for Windows weren't available. At least the support for Nano server. We are watching that. But every other builds are able to do it. Great. Nice. Thank you for that. Kevin, Mark, Damian, anything else to add before we close? No. Okay. That's a wrap up. Thanks a lot for being here. Oh, yeah. Go ahead. Thanks for driving that. Thanks. Thanks very much. You're welcome. The recording should be available from 24 to 48 hours. And see you two weeks from now. Bye-bye.


Master of the Union of Subjects, Sessions, Republic. It's been a very, very long time since I last seen you and you here. I know that you're here. Mrs. Dutton. And, uh, I have a question for you. Nice to see you, Mr. Bassard. How are you? How are you? Nice to see you. How are you? Nice to see you.   And also some remarks of mine. I hope this instrument will work. You know, thank you very much. Well, I hope that we can find a suitable date. Continue the meeting. We started meeting. Just a couple of minutes. All right, well, let's get your picture with your wife. And then we'll sit down. Yes, sir. So, President, we'll get one picture of you sitting there. Oh, good to see you, my friend. They're here. Take a chair there. Thank you very much. Religious meeting with you. Well, I'm honored, sir. We'll talk in a minute. We'll talk to you a little bit about that. Excuse me. You've been married in the same situation. No, I get the floor. Nice to see you. Carol, how are you? Good to see you again. I'm good. It's just become more and more evident that the choice there is a complete communist state in the establishment of the same. We've had some visitors in recently from Latin America and some right from Managua. And now the evidence is just overwhelming. I know we've been subjected to a disinformation campaign, but the evidence of the repression and how it has grown there, particularly against the church and religion, is when I say the church, we know that the predominant church is the Catholic church, but also what they call the evangelism. That's their name for anything Protestant. Well, the Protestants are taking that on the chin also. And they've gone so much further. A Monsignor was in recently, and he told me that in reality, if they were free to speak, that just the overwhelming majority of the people looked to us as the only saviors on the horizon. And we still feel that what we're trying to do. Hi. Hello, Mr. President. How are you? I'm good. Where do I sit right now? Right next to you. Right next to you. Right next to you. Let's get this stuff for law now. Thank you, Roy. This is a little room. The reason we're not in the Oval Office, if they're in there, turn it all to the television. That's to come up. So this is where I hide when I have opportunities to hide. It's good that you have a place to sit. Second-term members of the coverage don't have that. How many of us in North Carolina? Yeah, that's right. Let me say that I spent yesterday traveling, packed up the drive most of the time. And I regret that the speaker did not act differently on your request. I think that that's what a good thing to do. I guess you're going to get the last word. I'm sure you're going to go to the tube at noon. Yeah. And that will, I'm sure, get a lot of your phones jingling. I still have an overmind. I think that my vote on the salt tube last week indicates that I try to find ways to support my president. I don't remember my party and my delegation. And some of the problems which I have had about this. Hi, Floyd. Well, hello there. Hello. How are you? Hi, President. Congratulations. Thank you very much. That's true. We're thrilled for us to be here. Well, I think it's real bad. No, this is more than that. No. Well, please see me here. Well, please see me here. I haven't had any trouble. We're going to see if we can fix that. But I was thinking maybe I could get a lesson from you. I hear you're pretty nice with the putter yourself. Well, now it's a rather unusual putter. Did you really want to see? I've heard that you have something you'd like to show me. I'd like to see that. You could almost use it for fishing. That if you saw it was going over the rise of the Panthers, it's far you could intercept. That would be great for fast greens. We used a model just like on occasion. That's very popular now. We got one here with no strings on it. Just right. So that you really get in there and want to cut up a ball into one piece. A couple other balls there you can practice with. I know you have all that spare time on you. Stand down and put up a hunting ground. Well, you've got enough grounds around here. You should be able to stick one in. Kind of a pitching point course out there. Personalizing how we had a green today. I guess he could hit about, I'd say, 6-8 yards. Pitching is pretty good. I'm surprised President Ford didn't put it back in when he was here as well. John Orser here with the U.S. office. Nice to meet you. Hello, sir. Thank you so much for seeing me right. Please see we'll hand you here. We've brought you something from the Gulf House Museum Library. This is the first print. A limited edition print from our museum. I hope you can find this part. I certainly will. We have that frame right now. Well, that's wonderful. Thank you. Yes. You're not going to go out there. Thank you. Thank you very much. You can use that putter on some of those unwilling cemeteries on the contrary. How about that one? Is that the right plug, though? Like anything will work across the name, won't it? What a sander I have. Yes, sir. Okay, Tiff, brace yourself. I'm sure that it's often to try and tell a story to a guard that you probably know them all. The story of the fella that sliced him out of bounds. I was told when he got down there, at least when he was standing waiting with the bones. I have a harvest. He says you're going to ECS. He says the car you hit was a police car. And I said, I'm sorry. He says, what do you think you're going to do about that? I said, well, I figure that if I roll my right hand. Appreciate it, Maria. I really appreciate you having us. Well, listen, we're pleased to have you here. Did you get it? Yeah, but it'd be nice to do that. Did you get the middle of that? It'd be nice to picture it. It's prettier that way. There. Thank you, sir. Thank you very much. Thank you. It's a great pleasure. Nice meeting you. Real pleasure. Thank you. Our oldest U.S. open channel. Can't look too bad to me. Thanks, Mom. Could we have a picture with you? Sure. Would that be a thank you? With all of the presents? Sure. It would be wonderful. With Maria? Yeah. How about you three guys? Here's the house golfer. We'll get them in the middle. That's what they should be. Thank you so much. I appreciate it. Thank you. Good luck with the party. And for this. Have a wonderful trip to California. Whenever you can get out of here. Now it'll be tomorrow. Tomorrow. Good bye. Nice to see you. It's a pleasure. Thank you. Have a good night. Good night. Good night. Good night. Good night. Good night. Good night. Good night. Good night. Good night. Bye. Where do you all... You know Jack... Hi. Hi. before about this, but I think the situation has changed somewhat, and I'm going to try again to get the contract aided and so on. Because I know that there wasn't a feeling that you shared that maybe you were just simply entrenched in these things. I'm further in doing this, but that's not true anymore. Now we've got a close touch with the president of the other four democracies down there, and those presidents believe now that it's actually necessary that we provide that aid to their total support. And we've had some other people in here, religious figures from the Uraba, and down here and it's how much worse it has become. Well, we're very pleased that you would take a few minutes to visit with us. Well, I believe that you came down. I know since the last time in the other vote there's been a signable change. What we're talking about is this amendment. You have to remember down the vote that these fellows have put together with $300 million for aid to the other four democracies, non-military aid. And then the hundred million for the other thing is all that money, none of that money is new money. All of that is money already appropriated. $300 million is some state department, some AID, funds of that kind. And as you know, the other is kind of from defense. But we just feel that it has reached a point and now the whole situation has developed further down there to where, in spite of all the disinformation that they are most successfully putting out, all four presidents of the other court in line, she's worried quite a lot because we could sell away our hundred million. When I got her back, I said, where was I in the store? We were kind of off the river and let me finish the story before she registered. We've got conversations about the telephone wire. It's with the children. We have a station wagon full on Manana. On the way out to the ranch, I found out that I could hear the telephone wires and I would start telling them all about all the conversations that I was hearing with themselves. Can you take out stories as you remember them? Long yes, yes. More than anybody you know. That must be our story quite a bit. I took a picture of you here with Walter Cronkite at all of your closest circle and you were all laughing and having a wonderful time.


US warns allies are battle-ready in Asia. American forces and their allies in Asia are ready for a battle after years of joint combat exercises, a United States general said, adding that Russia's setbacks in Ukraine should serve as a warning to potential Asian aggressors like China and North Korea. US treaty allies, like the Philippines, Japan and Australia, among others, have shown that they will band together, that they will not stand for aggression from these nations, that have decided they want to change the world order out here, Major General Joseph Ryan said. Although Asia has no counterpart to NATO, the 30-nation military alliance, whose mostly European members vow to defend each other against external attacks, a network of US treaty alliances and defence partnerships upholding the international order, provides a regional safeguard, he said. I'm personally very buoyed by what I see by our allies and partners in this region and the way we've come together in response to aggression by the PRC, by North Korea, to say we will not let that stand. Ryan told the Associated Press in an interview using the acronym for China's official name, the People's Republic of China. In the broader Asia-Pacific region, Washington has reinforced an arc of alliances to counter what it says are threats posed by an increasingly belligerent China and North Korea. China has frowned on combat exercises involving the Americans in coastal areas, facing the South China Sea, which Beijing claims virtually in its entirety, and has accused Washington of meddling in Asian disputes and dangerously militarizing the region by regularly deploying US Navy warships and jet fighters. More recent venues of large-scale exercises by American and Filipino forces included coastal Philippine provinces close to the disputed South China Sea, where China has taken increasingly assertive actions to cement its territorial claim and in the northern Luzan region, which lies across a narrow sea border from Taiwan. That does provide some deterrent effect against an adversary in the region who would look at that and say, I don't want to take a step that may cause a government, a politician, to decide to go because I don't know that I can win. If I've got to face that trained ready force, Ryan said, while military commanders say the joint exercises are not directed against any particular country, Ryan said China's increasingly aggressive actions were an alarming reality the region should brace for. Does the backdrop of PRC aggression enter our minds when we train? Absolutely, he said. And in the case of the Philippines, US forces needed to be ready to fulfill their obligations under the 1951 Mutual Defense Treaty. We feel duty bound to ensure that the Philippines can maintain and will maintain their sovereignty, Ryan said. So aggression from the People's Republic of China that makes our treaty ally uncomfortable makes us uncomfortable.


It seems like we are seeing multi-stakeholder forums everywhere. From climate change finance to forestry policy to ecological restoration initiatives, organizations and governments are holding lots of meetings for stakeholders to discuss and make decisions. But not everyone gets an equal voice. Women and Indigenous peoples face many barriers. Cultural norms often prohibit women from speaking in front of men, and household duties may keep them at home. Lack of confidence and lack of experience hold them back. Indigenous peoples' knowledge and perspectives might be dismissed as unscientific. Distance and cost make it hard for them to attend, and often they are not even invited. How can we make multi-stakeholder forums more equitable and inclusive, and maybe even a force for change? Getting it right was developed to support organizers and implementers of multi-stakeholder forums. It is a step-by-step guide that provides them with tools to address these barriers and improve the inclusion of women, Indigenous peoples, and other underrepresented and often excluded groups in their planning, decision-making, and activities. The guide applies lessons learned from over 150 articles and over 60 interviews with practitioners around the world to understand what key actions can be taken to improve inclusion. It uses a rights-based approach, which means supporting the rights of all stakeholders to participate, especially those who traditionally have been excluded. By working together to improve inclusion, the organizers and participants in multi-stakeholder forums can make sure that everyone has space at the decision-making table, and that we get it right. You can download the guide from this link.