 Hello everyone, just a quick think-up today, so welcome to the open planning meeting, evergreen open planning meeting, sorry. So today I just wanted to make a quick think-up, even if there's not a lot of activities these days, but it's going to be improving in the next few weeks normally. So I just wanted to discuss quickly the latest merges into the evergreen cut base, but many was updates. So evergreen has been updated to the latest buzzeries, so that's one nice thing we discussed in the various talks you probably are possibly attended, but basically without having anything now evergreen has been updated on the various instances running out there. So the advisory that was published a few hours earlier is now deployed on the running instances, and so that's probably the main thing. The other important thing that was deployed recently, for which we are very much interested in feedback, is the one about the latest pipeline, but mostly mainly the bump of workflow support, which is a very important milestone, not for evergreen per se, but for Java 11 support for Jenkins, because at some point, so we are on another initiative in the Jenkins community, we are moving towards general availability for Jenkins running on Java 11, which is now not the case, we are still in what we call the preview mode. And so the 3.0 of the workflow support plugin was a real issue that we had until recently about deep technical serialization issue in the workflow support dependency that's called Jable Smarshalling, so after an update, the pipeline team was finally able to find a way to make this compatible, so now the good thing is that we can deploy that fix right away on as normal as usual, and it's going to be deployed on to the even the currently running Java, Jenkins running on Java 8, for instance, because it's compatible with Java 8, but the good thing is that then, when we, contrary to the previous state, when you will be running or upgrading to JDK 11, you won't have to do anything with regard to specific support for pipeline plugins, which is really, really simpler, because then so there is a small issue about that, which I'm going to describe pretty quickly because it's interesting for anyone watching possibly. So given the fact that the Jable Smarshalling library, so from a higher level standpoint means that how the pipeline, Jenkins pipeline framework stores the running pipeline state while running to be able to support and to survive failure and restart in the middle of the pipeline, that's that live serialization is not backward compatible. That means that if you upgrade to the dispersion of the workflow support plugin, you just want for a one shot time to make sure you stop or you let your running pipelines finish before you apply that upgrade. But that's the only issue then, once you've applied it, next time you won't have to do anything special in that regard. I mean, it will work like before. So it's just a one shot issue that you have to, well, work around or well apply and then it works fine. So that's really great compared to the previous state where we had a specific plug-in versions only applicable and usable for Jet running on Java 11 and another one that was for Java 8, so that's going to be much simpler for everyone. I think that's mostly it. I'm going to finish, I guess, with a quick reminder that there is Java 11 flavor for Evergreen, that that's available for people interesting to provide any kind of feedback, and so it's pretty easy to be usable. So it's going to be just, let me think, you will, it would just use that thing, but using instead of Docker Cloud, it's going to be called Java 11 Docker Cloud. It's the one available under that tag here. So that's the one you would be using. But all the rest of the common is the very same. And then you would be running a Java 11 version of Jenkins. And we are really eager to wait for your feedback to hear for any kind of issue you would encounter running that flavor. That that's all I wanted to cover today. So thanks, everyone. Hi, Tyler. I hope my the sound was going through. And so anything else you want to discuss or cover before I'm going to stop skin sharing? Yes, I just want to let you know the the stuff that I've been working on. Just keeping the plugins up to date. I've been sort of doing that in between meetings. So I think I'll keep doing that. The foreseeable future. The there was another feature that is still on my to-do list as my free time progresses, we'll see what I'm able to do here. But there's it's a back end change right now. We only have a single deployment, a single deployed node instance for the Evergreen back end. I see what you mean. And then there's a logic called Feathers Sync, which would introduce a Redis dependency for the back end so that we would have we have the end number of Redis and we're not ready to say a number of Evergreen back end instances. Yeah, sports right over. Yeah. So that's that's the next thing that I'm interested in working on just because with 20 instances, I'm sure we're not seeing any problems right now. But that was a known a known trade-off that we made in the March to production. Yeah, that's next for me to do. I just want to let you know. So plug in updates and then that one are on my to-do list. Great. So indeed, I was talking, I don't know how at which at what stage you joined the meeting, but I was explaining at the beginning that we already applied or so the upgrade of the security release, the last plug in the dates. So that's when I think of Evergreen indeed that people don't have to worry about being up to date in terms of not only features, but also security. So that's when that's already applied to you. Yeah, which to me is super cool. Yeah. So thanks. And anything else you want to cover before I stop the broadcast, Tyler? There's one issue that I'm looking at right now. I'm going to go ahead and paste it in the channel. And that's related to recent versions of the branch API plugin and the kit plugin. And we actually just deployed these plugin upgrades on CID at Jenkins IO. So I'm going to see if those are failing. But those, if, you know, if this is a, if this is a real issue that we're seeing in production, then this would also affect Evergreen. Yep. Okay. This is just what I'm looking at this morning. So we'll see, we'll see what's up here. Right. Indeed. We need to probably have a look at that. We have, but that's, that's a nice point. We have automated tests, but I don't think we still have developed a way to, you know, run some, like some kind of smoke pipeline, smoke test pipeline, uh, during automated tests, which we would be pretty important and pretty critical to do at some point and rather sooner than later. Um, but yeah, we, we, we, right now we wouldn't be catching that kind of issues indeed. So that that's, that's a waste indeed. Yeah. All right. So anything else? Yeah. And so I'm going to stop the broadcast, I think. Okay. See you everyone and see you next week or something. Bye. See you later.