 And welcome to the third video in a series of three videos. On this last video, I will finish the webhook integrations from GitHub to OpenShift. And the final result will be that when I make changes from BRMS, the changes will be pushed out to GitHub. And the webhook that we have configured in GitHub will trigger a new build on OpenShift and we'll have our application change it whenever our file is changing in BRMS. So let's start first with BRMS. I'm going to open the file that I will change here. This is the file and I'll change it Hello. Instead of at your service my master, I will say Hello Rhetori UROC. Okay, this is it. Save. I call it IROC because I do. And then it's saving the file and it's pushing the change to GitHub. Let's see if we have the change here. We do have the changes IROC. So our webhook worked from BRMS to GitHub, which we've seen before. And now what we'll do is we'll come to GitHub and we'll add my trigger. So let's come to the builds and I'll copy the URL for the trigger, which is here. Just copy it and let's come to my repo then and let's add the webhook. Add webhook. This is the URL of my webhook. Does not require SSL and webhook add. So again, this will mean that the changes that I make to BRMS, they will trigger a build and deploy an open shift. Let's come to BRMS. Make sure that this is the file that I want to open. And I will say instead of UROC, I'll say you really rock because I really do rock. And I changed the file. Let's come to see if it changes. I do really rock and now let's come to open shift to my builds. And as you can see, a build just kicked out here and that will be for a change. So now the build is happening. And as remember, we have configured this project to use Maven as a proxy. So it's downloaded everything from Maven. Again, I really recommend you to do this. And now it's going to finish building the project. We can come here to my builds and see that we have the builds running. Here we can see the other builds and how long they took. This we can see this new build. If we come to the overview page, we'll see that a new build is running. And then we can see the logs. Let's check out the build logs to see how that's coming along. And it has pushed the image. And now the next step, after pushing the image, we know it's exactly running the pod. And this comes to the webhook trigger. Sorry, to the liveness probe, which I mentioned before. So now it's running the process. We can come here to the logs, follow the logs and wait for it to come live. While it does finish bringing the pod, I'll just go over again of what our B-R-M-S rules package is about. It's a simple rules package that takes a person. And whenever the person's name is Rhetori, he will say you really rock. And if the person's name is not Rhetori, he will say, hey, you get out of my way. And whatever person's name that is. So this is the full process. This is a change from B-R-M-S. The file goes to GitHub. The webhook trigger that we have configured in GitHub will tell OpenShift to issue a new build. And OpenShift will build our Docker image with the change. And then we'll deploy it. Let's come to OpenShift and see if our pod is already in a ready state. Yes, it's already state. So we can test it. I'm going to use Rhetori. And you should say that I really rock, which says that I really rock. So that's it. Our hooks worked. So we can see a change in B-R-M-S, trigger a new build, and deploy on OpenShift. Thank you very much.