 Hi, Steve Spiker here for the OpenShift team again talking again about some of the upcoming features in OpenShift 3.3 and the open source community origin 1.3 and some of these are features coming so not really slated and confirmed so What you see here may change some in the final product So I'm gonna show this again in the way of some roles certain roles of 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 mainline 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 was 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 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 of a similar view here A little different in this environment that I'm working. So this is working maybe more than a team integration Kind of environment where I'm actually running the front end on a and 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 this 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 poll 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 Wait 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 have it 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 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 and I've automated the entire Validation build containerized image deployed to an integration environment and then actually test it So thanks if you're looking for this the next video will show how you can get this up and running pretty quick