Red Hat OpenShift OpenShift 3 Demos, 7 Oct 2016

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Create Your Own Build Pipelines with OpenShift 3.3, Part I

Description

In this video, Veer Muchandi walks through the creation of a build pipeline for an application on OpenShift 3.3.

In Part 2 (https://youtu.be/tUqwKQsHLkY), learn to edit an existing pipeline for use across multiple projects.

A

A

Hello, everyone welcome to OpenShift videos in this video we'll we will learn how to create our own build pipelines in opposite version: 3 RT. This is an upcoming release coming in in the next few days. The version that I'm using right now is the pre-release version, so things might be slightly different than the actual release. You would have seen earlier. Videos on how pipelines work in open shoot version. 3.3 in this video you'll learn step-by-step on how to create your own pipeline for your application on run in the next video.

A

You will learn how to edit this pipeline to go across the projects. So, let's start simple. First, we'll learn how to create a pipeline. So, let's start by creating a new project I'm going to call this project CI CD you'll notice, a small change here, just like in the previous versions. You can process the catalog and deploy your own application. You can also deploy an image by clicking on this or you can employ import a channel or a JSON file for creating a Jenkins. Build configuration will import a yamo here.

A

This Y amel is a build configuration I call it. My first pipeline I'll make this available through my github, and this pipeline has. If you look at the strategy here, this build configuration, has the type Jenkins pipeline and it uses Jenkins pipeline strategy, and it is pointing to a Jenkins file, we'll discuss the contents of this file in a minute for now, I'll just go ahead and create once I did that you'll notice that there is a route Jenkins here and in a few seconds you will see that Jenkins part will start running here.

A

You go. The deployment is running.

A

And the Jenkins pod is up now. Let's look at this part from the environment. I want to capture this Jenkins password because in order to login to the Jenkins console I'll need this password.

A

Click on this URL here is my Jenkins console I login as administrator.

A

This is the first pipeline that we just created. Let's go back to our web console if I look at the bills, section you'll see the pipeline's here. This is the first pipeline. Let's see the configuration here is the Jenkins file Jenkins file. Let I wanted to talk about, so this Jenkins file has two stages. The first stage is the build stage and in the build stage, I'm running an open shift build and this build would invoke a build configuration called my PHP. You can edit it to some other name.

A

If you wanted to create an application with a different name right. The next stage is a deploy stage and in deploy stage I'm doing two things. First I'm invoking open ship deploy here a deployment configuration with the name, my PHP will be invoked and once the deployment is complete, I want to scale up this application to two instances very simple. Now, let's go back, we don't have at the build and deployment configuration for my application right. So in that context, let's use an application.

A

I have on my github a small demo, app that uses PHP, so I will copy this say: act a project select PHP because there's a PHP, app I'll name this. My PHP remember the name in the pipeline and I'll point to the git repository. Let's go to the Advanced Options and here I don't want the bill to be triggered automatically. So I am removing the auto trigger options as well as I. Don't want the deployment to happen automatically so I am removing the auto deploy.

A

Options is because I want these to be invoked by Jenkins rather than by openshift or mine. Go to +1 create the application. Is creative I'll go back to the console. Let's see that there is a bill created for my PHP.

A

There is a deployment created for my PHP and there is an image stream created for my PHP and once the build runs it's going to push the image into this image stream.

A

You will also notice that it created a service and a route for my application that is yet to be built in deploy. Now, let us start our pipeline.

A

This is the pipeline and I am going to start it. So the build is now getting invoked.

A

Let's look at the logs, it shows the logs in Jenkins console as the console output. The build is getting started. The build has just added. It has entered the stage, build.

A

Let's go back to the console, so each here it shows the pipeline I started now. I can also see this. On the oh, you page.

A

So the first step in the pipeline is complete. Build is completed in 50 seconds now the deployment has started. It is deploying one part once this is done. It goes and scales up to two parts.

A

Now that the build and the plummet is complete, let's look at our application and it shows the green rose.

A

Now, let's go back and make a small change. I'll edit this application core and I'll change. This green rose to bureaus commit to chains. Let's verify again, it's showing green rose. Now, let me start. The pipeline again starts the build.

A

The build is now complete and the department, so it's one of the one new power and the second new power.

A

Now that the build and deployment is complete, let us check our application. It shows a blue rose. That was a simple example of how you can create your own pipeline and run it within OpenShift, 3 or 3 in the next video we'll see how we can edit this pipeline to go across the projects will create a development project will create a testing project and we will do the built on the deployment and development and then move it into testing. Thanks for watching.