 Hello everyone, sorry for the mishaps for anyone who was watching the previous recording. So the previous video, basically so we got back into more specific demo because there's not a lot of things to discuss today apart from that. So, Adrienne is going to do a demo of Evergreen to, so Adrienne is going to be doing a demo of the Evergreen Java 11 Flavor, that's it, yeah, you can go on, Adrienne. Okay, so to start the Java 11 Evergreen Flavor, what you can do is use the normal Evergreen starting demonstration you can find on Jenkins.io website. Just replacing the tag with Java 11 dash docker dash cloud. And once you're there, you'll have your instance starting as usual in localhost on proc 8080. And so normally you should be quite fast because I already started. And when it started, you have your instance available. And to get the password, you use the normal command that you can also find on the website here. And here you have your Jenkins instance. And to make sure that you are on Java 11, let's show the logs, sorry. System information, just about here. System information. And here you can see that we are currently running on Java 11 01. And so I guess that's it. Yeah, I guess you can create a new item and start a build. Because if you, well, I guess there's something I think we need to change, but yeah. If you do that out of the box with the war that's provided out of the box on Jenkins.io, right now it would fail because you wouldn't get the right version of the plugin that's called workflow support. So that's something that's kind of fixed for you. We fixed that for you out of the box in the green. So you can just use the try sample pipeline on the right and you, hello world, it's nice for demos. Exactly. And so you would help, if you would do that on the usual download setup, it would crash pretty severely out of the box, right away. And so if my computer wants, yeah, it's going to take a few seconds to, so what happens in the background here is that it's actually pulling the official SSH agent, no, not SSH agent, Docker image, and spawning a Jenkins agent there and then connecting to it and then running the build inside and then throwing it away, like, as usual, in the Docker cloud flavor. Yeah. And it's worked, and it worked. So I guess we are fine for today. We're not going to get back to the status meeting because there was not a lot of things moving for the last week apart from this. So thanks everyone for watching and we'll hopefully get back with more news next week about Evergreen. And obviously, if you have any questions about Evergreen General, feel free to go reach out to us on our Gitter channel under Jenkins-infra slash Evergreen. Thanks everyone and see you next week. Bye. Thanks everyone.