 Hi, Steve Spiker here for the OpenShift team again. I'm gonna show this again in the way of some role, certain roles that people play in scenarios. So now I am Steve, a devops engineer, and I just received some code from a friend, one of the colleagues, so this new guy Joe, and it makes me a bit nervous about what he's up to because I heard he may have not, he may have left his previous employer not on the best terms for some of his loose antics. So let's, but I'm feeling pretty confident because I've set up a pipeline here to help validate what our mean line code is. So I'm gonna go through and it's gonna validate a poor quest and it's going to build a source code once it's been done some sanity checks. And so here we go. Well, I could do this with kicking it off, you know, through GitHub integrations. I could kick it off manually. I could kick it off on a regular basis. So I'm back to the overview and like the overview we've seen all before, Joe just had this left-right view of the front-end service in the back-end database. So a similar view here, a little different in this environment that I'm working. So this is working maybe more in a team integration kind of environment where I'm actually running the front-end on an auto scaler. So I see it goes scales down the one and goes up to four based on the amount of traffic I receive. At the same time, it's actually I can see what various pipelines that are currently going on. So a quick summary of what the current latest ones are. It's I see now it's it's moving along the build process here to generate, you know, the new containerized application image that incorporates the base secure layer that we've had and then also the new application code that flew in from this pull request. And as that's building, it'll update and then the next step in the process will actually trigger deployment. And so we can see that there's a rolling deployment here. So as it's spinning up the new version, it then waits for that to be live and receiving traffic and then it'll shut down the old one. And then next to my pipeline, I'll do some habits such that the next stage will do some Sandy checking and validate the integration environment through some of the automation I have. So through all this I've really been able to automate the safe experimentation that new people like Joe come into the platform and I don't have to worry about how they're going to affect my process. I've got a plan in place and a pipeline here to help build and I've automated the entire validation build, containerized image deployed to an integration environment and then actually test it.