- [Presenter] Okay, welcome back. In this demonstration I'll create a new front end build config, configured to use the S2I front end builder image. And configure it to build the front end source code located in the OpenShift vote app front end react GitHub repository. Now, before I proceed with step 22 it is highly recommended that you fork your own copy of the OpenShift vote app front end react GitHub repository, and update the git URI field within the build config that we are about to create with your own forked repo URL. The main reason for this is that later on in step 27 I'll show you how to trigger automatic builds using a web hook configured within the GitHub repository. 

By having your own forked version of this repository you'll be able to point the web hook at your own cluster, and be able to push code updates triggering an auto-build of the front end within your cluster. More on this later. For now let's jump into step 22 and I'll copy the build config as is, and execute it directly within the terminal, like so. Excellent. This has created a new build config within the cluster. We can see this by examining current build configs, by running the commands, OC get buildconfig. And OC describe buildconfig frontend. The last command in particular shows the finer details of the front end build config that we just created. Take note of the web hook URL. 

This needs to be copied and will be used in step 25. Now that the front end build config is in place, we are almost ready to run our first front end image build within the OpenShift cluster, using the S2I front end builder image. But before we do we need to create a new image stream for the front end images that the build system will create. To do this, I'll copy and run the command in step 23, like so. I can again examine the list of available image streams configured within the current cloud academy project, by simply running the command, OC get IS. We're now ready to run our first front end build within the cluster. Let's go ahead and do this by copying the command from step 24. And executing it within the terminal like so. This command will actually tail the build from start till finish. I'll sit on the tail and wait till the entire build run completes successfully. 

Excellent. We can see that the build has just completed successfully. This should have resulted in a new front end image, which will have been pushed into the previously created front end image stream. We can check this by running the command, OC describe IS frontend. Or alternatively by looking within the OpenShift web admin console. Clicking on build configs we can see our front end build config. Clicking on it, we can then see it's details, and under builds we can see each of the builds that have been performed. Here we can see just the one, which we had just kicked off. Clicking on it, we can see the build details, such as the memory, CPU, and file system usage. Additionally, under logs we can see all of the logging as omitted by the build. This is is extremely useful for debugging broken builds. Clicking on image streams, we can now see that we have a new front end image stream, which contains our newly built front end container image, a perfect result. 

Okay, that completes steps 22, 23, and 24. We're now ready to move on and set up the front end deployment config, which will utilize the front end image that the build has just generated for us.