Configure pipelines configure-pipelines

Explore the different types of pipelines in Cloud Manager and how to configure them for a successful project.

Hello everyone my name is Varun Mitra and welcome to the video. In this particular lesson, we will talk about Configuring a Continuous Integration Pipeline in Cloud Manager. After completing this training, you will be able to configure a continuous integration pipeline and configure Release Branches. One of the key capabilities of Cloud Manager is the ability to exercise and optimized CI/CD pipeline to speed the delivery of custom code or updates such as adding new components on the website. So, the cloud manager UI customers can configure and kick off the CI/CD pipeline. During this pipeline execution a thorough core scan is executed to ensure that only high-quality application pass through to the production and . You can easily set up configure and kick off CI/CD pipeline and increase deployment frequency from month, weeks to days and hours. In addition to the main pipeline which deploys to staging and production, customers are able to set up additional pipeline referred to as non-production pipelines. These pipelines always execute the build at good quality step. They can optionally also deploy to Adobe managed services environment. So now let’s just quickly go ahead and see how you can set up CI/CD pipeline in Cloud Manager. So, this is my Cloud Manager instance. Right over here you can see that I’ve got two different kinds of pipeline, I’ve got a production and a non-production pipeline. Now if I want to edit the settings I can quickly go to the edit button, by going over here I can change the gate branch that is associated with my pipeline. If I had more branches I would have been able to switch between them. Right now, I have just two so I have selected the weekend branch right over here. In addition to this I can also set up different environments settings For example I can change the deployment trigger. I can specify important failures behavior and I can change the production deployment settings. In addition to this, I can also specify different testing criteria that is what kind of testing I want to perform on my side once it is ready for go-live. Right now, my testing criteria is set to test three different kinds of pages that is popular like pages, other like pages and new pages. I can toggle these switches on or off to change the percentage. Finally, I can save my changes. I can perform the same settings for the non-production pipeline, I can also add a new pipeline over here that is I can add a new code quality pipeline. I already have two deployment pipelines so I won’t be able to add a new one. So, I can specify upload quality pipeline over here, provide a name and specify the Git branch. Once I do that I can also specify the deployment trigger and I can save these changes. So, once I’ve set up the non-production or a code quality pipeline, I can execute it independent of rest of the pipelines that I have bought over here. As you can see, I’ve got two different nonproduction pipelines or actually three different non production pipelines. Two of them are code quality pipeline and the third one is a deployment pipeline. So, I can have only one deployment pipeline that is going to deploy code onto my actual and live instances and you can see that it is right now running or and it is on the build image stage. However, I can add as many code quality pipelines as I want and I can have them configured on different Git branches. So, if I want to test out code from different gate branches I can create multiple non-production pipeline and have them run through different branches or different piece of code. I can also run them independent of each other. So, for example I can run the non-production pipeline and I can beat for its result. Now, this is how you can set up production and non-production pipeline. Keep in mind production pipeline will perform a deployment on your staging and production environment, they will have different steps associated with them whereas a non-production pipeline can be a code quality pipeline or a deployment pipeline. A deployment pipeline as the name suggests will perform a deployment on the Dev or QA instances and the code quality pipeline will perform good quality scan on your Git branches. Now in addition to this you can also see that there is a Manage Git button. This particular button will give you access to the Git repository. This will provide you with a URL pointing to your Git repository, you can copy this and using command line or using GitHub desktop you can clone your Git repository very easily. In addition to this, this would also allow you to generate a personal access token which your developers can use for cloning and pushing code to your Git repositories. So this will make your Git repository management a lot more easier, it would provide your developers a direct access to your Git repository so that they can access it, so that they can download and they can push the code to this particular Git repository. So, this is how you can manage your production and non-production pipeline. So now you should be able to configure a continuous integration pipeline and configure Release Branches. Thank you very much for watching this video and have a great day. -