Jenkins Pipeline Job Configuration and Review Pipeline Results
A free video tutorial from Nand V
Cloud Application Architect
4.1 instructor rating • 1 course • 2,313 students
Learn more from the full courseDevOps with GIT(Flow) Jenkins, Artifactory, Sonar, ELK, JIRA
Complete Hands-On DevOps course that will demonstrate efficient use of DevOps Tool Chain
06:37:49 of on-demand video • Updated January 2019
- Build DevOps environment for their organization.
- Expand the DevOps environment for multiple use cases in their organization.
- Identify DevOps toolchain fit for their organization and customize as needed.
- Full fledged environment setup for major categories in DevOps toolset.
English [Auto] OK. So now that we have checked in the code let's go ahead and create pipeline job within Jenkins. So go ahead and select new item and let's named item name as a pipeline because this is going to be running off to a branch which is the default branch. Let's go ahead and click on Pipeline and let's go ahead and say OK. So once this has been loaded we are going to configure it to listen to the changes on the devil up branch in a typical environment you're going to do those where there is a Crigger on the ACM that sends a notification to Jenkins to say that hey I have a new change and go ahead and trigger this job. In my environment since I'm running Jenkin's locally and my get repository is on the internet I do not have that flexibility but you can set it up in such a way that if you have a Jenkin's instance running on a private cloud or an AWOS cloud you should be able to do is invoke the job through the change through F-in in this code. We are not going to talk about configuring the triggering of the job but we are just going to concentrate on the triggering of the pipeline job. OK so now that we have the pipeline job created Let's go ahead and configure it and say that we are going to use the pipeline script from a Seann and the repository is good. And we're going to provide it to get rep or you are all going to copy that. And my branch specifier would be Deborah. And let's go ahead and say apply make sure that you do the unchecking on the lightweight check out descript but Jenkins file that's where we come into the Jenkyns files to the root of the project. Let's go ahead and say apply and go ahead and do it. Let's build the project. And as this is building you will see that you can visualize those different states of the pipeline. So it went through the prepared stage and now it's going to the build stage which basically is the main one clean package. And once this is done through the back stage it should go through the unit test stage. Then the integration test then the sonar and then the deploy and the smoke test in a real world environment the way you would be setting up the pipeline jobs. You'll have a monster node for the Jenkins instant and you'll have several worker nodes for supporting the bells. So the master node is basically kind of an orchestrator that's going to kick off the jobs and let the workers do their jobs. So right now it went through the integrated Russian state. And so now our. And once it's gone through the sonar it's going to go through the deploy. And at this point if we head over to sonar and let me go ahead and refresh it and I had to double up and I should see the activity that it just pushed the latest changes to the apothecary and it's finished. This knocked us so we have basically feyne how we can use to Jenkins pipeline to visualize the different stages of the build process.