 Hello everyone So welcome to the evergreen open planning meeting We are going to have a quick status of our what's happened last week and I think last week. I think I was absent. So you had a status with Tyler by the way, Amanda. I think I don't remember if it happened Okay So No, it's not in French Yeah, because yeah, I think I pasted so just for you to know Matt you are live and it's recorded So and I will just explain afterwards if you want some details about what this mirror anyway So for anyone watching this is the open planning meeting for evergreen So it's open to anyone and it's operated in public. So it will be automatically posted than the Jenkins YouTube channel after it. So and it's also watchable live. So right now we have nobody watching but Sometimes it's the case. Anyway, so I'm going to share my screen and so we are going to basically have a status An open status, so I'm going to show and first Open the board and sharing my screen right now so for people watching we do that once a week and try to share the Yeah, so the status of evergreen project and where we are and so what people have been doing and what are the challenges or yeah And it's roughly in theory between fifth. It's planned to be 30 minutes, but it's often less so It's a short and in probably interesting to watch if we if you're interested about the evergreen Initiative so and I have a crap in it work today. So it's not happening. I should have opened that before The choice of computing So for people watching again, this is our board We are right now on what we call my stone to the milestone one was more something we did to make evergreen usable At least in kind of alpha mode for mainly Jenkins world they was forward in San Francisco and then nice in France So right now the status is that it's usable, but it's not really prediction ready yet We have a lot more things to tackle to make it so so Let's start with you Mandy. So how do you have any update to share today or no at this point? I'm mostly just doing pull request reviews We probably could go ahead and unassign those tickets for me for somebody else to pick up Yes, so for people watching we might have some more people joining the initiative in the next few weeks But it's not very crystal clear right now. So I'm not going to talk about that too much right now So I'm going to make a quick status on what I did recently So I fixed the AWS flavor recently and I hope to be able to reach soon. So this is that one We are about to have incrementally fired Russian Which means that in the next future, but I hope for I hope very soon We will be able to update to last latest blue ocean on each merge commit because we then will have the infrastructure to Automatically publish a release a special release for each merge Which is already the case for ec2, which has been by the way recently fixed and merged by the way by Matt Who's here right now. Thanks Mac Matt for this And so what I've been Doing recently is that so I fixed that and I discovered a few issues here and there and so we've been bumped yesterday by the way the versions for the security release so right now ever green is up to date and The recent updates about ever green the main one has been there So the rollback and I need still to work on the data part of it And I guess that would be it and for AWS. I guess the next Not that big in terms of things to do I guess but in terms of feature would be to do Do that one that one would be nice. So maybe I will be the one doing that or I Pass that to someone else but basically have some way to make the cloud version template, which is currently usable Usable by is more easily, you know by some click button on the evergreen website So that we can then update that page and have you know Genkis users have a link right here that will redirect to their AWS accounts and be able to write our web version the next and evergreen instance running and then there would be a sliver and And Yes, that's mostly it for me and you can see here on the left We clarify that recently by the way. There's a few Giras that are on a side, which means basically nobody is working on it So we try recently to clarify and you know and assign ourselves from the thing. We really didn't plan to work on Soon that thing has been by the way tackled by that Contributor, which is one of the first things first contribution external contributions. Thanks again for your hand And I think it's merged if that thing wants to load at some point I'm pretty sure it's merged. Is there any here anyway? Oh, I think it's the case so it's a nice contribution and it was a Probably a hacktober or something fast act of a fast hack. I guess so, yeah I Guess we are that's it for this week mainly I'm going to ensure Do you have anything else to share or springing in mind Mandy or Matt I mean I brought up something on Jenkins devil is recently that could be useful forever green It's kind of part of Jenkins Jolt in general trying to introduce some more a more useful feature flagging system in Jenkins so that we can introduce Changes kind of my gradual changes through continuous delivery Instead of having to coordinate multiple plugins for various features and things like that It'll be a kind of an interesting thing Try to get some feedback on Yes, um, so I saw it from far away. I didn't to be honest digging to it. Uh, yes, we've been discussing a few Times in the past the feature flag. It was supposed to be worked on by that architecture team But I'm not sure where we are. There was that beta which was it was a really feature flagging that beta thing Annotations and plugins so that people would have you know to explicitly Subscribe to some feature but yes, I guess I need to read your proposal and everything but Yes, we definitely would need our yeah Have some feature flagging at some point because it would allow us to you know progressively or you know more aggressively deploy Things in production, but you know that without meaning that thing it would be you know usable by the whole target Though in the case of evergreen, I guess that it's slightly We have other ways. We are complementary ways to achieve that kind of partial deployment by you know At some point writing the code that would allow us to do some kind of canary deployment Which then would allow us you know to have some Only a subset of versions that would be up to date, you know on the latest update level, I guess But yes, I guess at some point it would make sense definitely for people watching and for you Matt for your information right now we have the the database structure and the data structure right now to allow many channels, but we for I guess capacity reasons and everything and then at that stage We only have one channel country configure current configure and configure right now, which is the name general But we do have that channel logic Developed in the code normally so it's not better tested obviously because it's not used But it's supposed to be usable so I hope that soonish we will be able to run, you know some Canary channel for our own testing instances and we will be able to you know detect crap before it goes to the let's say alpha channel then general channel or whatever Oh Yeah, I hope we are able to accelerate at least a bit so that we can reach More than a alpha state right now because right now we have a state that is Roughly usable would say because I've I've done it myself a few days ago And I'm planning to do a few things using evergreen myself Which is a state I guess we are about to reach or have reached but yes if there's still A lot of rough ages I would say Okay I guess we are going to stop in not because I couldn't labor forever. So I'm going to stop the Broke task right now and thanks everybody for watching and see you next week