What is Continuous Delivery Continuous Delivery Pipeline Using Jenkins

What is Continuous Delivery Continuous Delivery Pipeline Using Jenkins Continuous Delivery Tutorial Building A Continuous Delivery Pipeline Using Jenkins Back Home Categories Online Courses Mock Interviews Webinars NEW Community Write for Us Categories Artificial Intelligence AI vs Machine Learning vs Deep LearningMachine Learning AlgorithmsArtificial Intelligence TutorialWhat is Deep LearningDeep Learning TutorialInstall TensorFlowDeep Learning with PythonBackpropagationTensorFlow TutorialConvolutional Neural Network TutorialVIEW ALL BI and Visualization What is TableauTableau TutorialTableau Interview QuestionsWhat is InformaticaInformatica Interview QuestionsPower BI TutorialPower BI Interview QuestionsOLTP vs OLAPQlikView TutorialAdvanced Excel Formulas TutorialVIEW ALL Big Data What is HadoopHadoop ArchitectureHadoop TutorialHadoop Interview QuestionsHadoop EcosystemData Science vs Big Data vs Data AnalyticsWhat is Big DataMapReduce TutorialPig TutorialSpark TutorialSpark Interview QuestionsBig Data TutorialHive TutorialVIEW ALL Blockchain Blockchain TutorialWhat is BlockchainHyperledger FabricWhat Is EthereumEthereum TutorialB lockchain ApplicationsSolidity TutorialBlockchain ProgrammingHow Blockchain WorksVIEW ALL Cloud Computing What is AWSAWS TutorialAWS CertificationAzure Interview QuestionsAzure TutorialWhat Is Cloud ComputingWhat Is SalesforceIoT TutorialSalesforce TutorialSalesforce Interview QuestionsVIEW ALL Cyber Security Cloud SecurityWhat is CryptographyNmap TutorialSQL Injection AttacksHow To Install Kali LinuxHow to become an Ethical Hacker?Footprinting in Ethical HackingNetwork Scanning for Ethical HackingARP SpoofingApplication SecurityVIEW ALL Data Science Python Pandas TutorialWhat is Machine LearningMachine Learning TutorialMachine Learning ProjectsMachine Learning Interview QuestionsWhat Is Data ScienceSAS TutorialR TutorialData Science ProjectsHow to become a data scientistData Science Interview QuestionsData Scientist SalaryVIEW ALL Data Warehousing and ETL What is Data WarehouseDimension Table in Data WarehousingData Warehousing Interview QuestionsData warehouse architectureTalend T utorialTalend ETL ToolTalend Interview QuestionsFact Table and its TypesInformatica TransformationsInformatica TutorialVIEW ALL Databases What is MySQLMySQL Data TypesSQL JoinsSQL Data TypesWhat is MongoDBMongoDB Interview QuestionsMySQL TutorialSQL Interview QuestionsSQL CommandsMySQL Interview QuestionsVIEW ALL DevOps What is DevOpsDevOps vs AgileDevOps ToolsDevOps TutorialHow To Become A DevOps EngineerDevOps Interview QuestionsWhat Is DockerDocker TutorialDocker Interview QuestionsWhat Is ChefWhat Is KubernetesKubernetes TutorialVIEW ALL Front End Web Development What is JavaScript â€" All You Need To Know About JavaScriptJavaScript TutorialJavaScript Interview QuestionsJavaScript FrameworksAngular TutorialAngular Interview QuestionsWhat is REST API?React TutorialReact vs AngularjQuery TutorialNode TutorialReact Interview QuestionsVIEW ALL Mobile Development Android TutorialAndroid Interview QuestionsAndroid ArchitectureAndroid SQLite DatabaseProgramming Development, Testing D eployment Technologies Involved In DevOps Git Building A Continuous Delivery Pipeline Using Jenkins Last updated on May 22,2019 7.6K Views Saurabh Saurabh is a technology enthusiast working as a Research Analyst at Edureka.... Saurabh is a technology enthusiast working as a Research Analyst at Edureka. His areas of interest are - DevOps, Artificial Intelligence, Big Data and... Bookmark 3 / 7 Blog from DevOps Lifecycle Become a Certified Professional Continuous Delivery:Continuous Delivery is a process,where code changes are automatically built, tested, and prepared for a release to production. I hope you have enjoyed my previous blogs on Jenkins.Here, I will talk about the following topics::What is Continuous Delivery?Types of Software TestingDifference Between Continuous Integration, Delivery, and DeploymentWhat is the need for Continuous Delivery?Hands-on Using Jenkins and TomcatLet us quickly understand how Continuous Delivery works.What Is Continuous Delivery?It is a p rocess where you build software in such a way that it can be released to production at any time.Consider the diagram below:Let me explain the above diagram:Automated build scripts will detect changes in Source Code Management (SCM) like Git.Once the change is detected, source code would be deployed to a dedicated build server to make sure build is not failing and all test classes and integration tests are running fine.Then, the build application is deployed on the test servers (pre-production servers) for User Acceptance Test (UAT).Finally, the application is manually deployed on the production servers for release.Before I proceed, it will only be fair I explain to you the different types of testing.Types of Software Testing:Broadly speaking there are two types of testing:Blackbox Testing:It is a testing technique that ignores the internal mechanism of the system and focuses on the output generated against any input and execution of the system. It is also called functional testing. It is basically used for validating the software.Whitebox Testing:is a testing technique that takes into account the internal mechanism of a system. It is also called structural testing and glass box testing. It is basically used for verifying the software.Whitebox testing:There are two types of testing, that falls under this category.Unit Testing:It is the testing of an individual unit or group of related units.It is often done by the programmer to test that the unit he/she has implemented is producing expected output against given input.Integration Testing: It is a type of testing in which a group of components arecombined to produce the output. Also, the interaction between software and hardware is tested if software and hardware components have any relation. It may fall under both white box testing and black box testing.Blackbox Testing:There are multiple tests that fall under this category. I will focus on a few, which are important for you to know, in order to understand this blog:Functional/ Acceptance Testing: Itensures that the specified functionality required in the system requirements works. It is done to make surethat the delivered product meets the requirements and works as the customer expectedSystem Testing: It ensures thatby putting the software in different environments (e.g., Operating Systems) it still works.Stress Testing: It evaluateshow the system behaves under unfavorable conditions.Beta Testing: Itis done by end users, a team outside development, or publicly releasing full pre-version of the product which is known as beta version. The aim of beta testing is to cover unexpected errors.Now is the correct time for me to explain the difference between Continuous Integration, Delivery and Deployment.Differences Between Continuous Integration, Delivery AndDeployment:Visual content reaches an individuals brain in a faster and more understandable way than textual information. So I am going to startwith a diagram which clearly explains the diffe rence:In Continuous Integration, every code commit is build and tested, but, is not in a condition to be released. I mean the build application is not automatically deployed on the test servers in order to validate it using different types of Blackbox testing like User Acceptance Testing (UAT). In Continuous Delivery, the application is continuously deployed on the test servers for UAT. Or, you can say the application is ready to be released to production anytime. So, obviously Continuous Integration is necessary for Continuous Delivery.Continuous Deployment is the next step past Continuous Delivery, where you are not just creating a deployable package, but you are actually deploying it in an automated fashion.Let me summarize the differences using a table:Continuous IntegrationContinuous DeliveryContinuous DeploymentAutomated build for every, commitAutomated build and UAT for every,commitAutomated build, UAT and release to production for every, commitIndependent of Continuous Deli very and Continuous DeploymentIt is the next step after Continuous Integrationit is one step further Continuous DeliveryBy the end, the application is not in a condition to be released to productionBy the end, the application is in a condition to be released to the production.The application is continuously deployedIncludes Whitebox testingIncludes Blackbox and Whitebox testingIt includes the entire process required to deploy the applicationIn simple terms, Continuous Integration is a part of both Continuous Delivery and Continuous Deployment. And Continuous Deployment is like Continuous Delivery, except that releases happen automatically. Learn How To Create CI/ CD Pipelines Using Jenkins On Cloud Become A Certified DevOps Engineer Now But the question is, whether Continuous Integration is enough.Why We Need Continuous Delivery?Let us understand this with an example.Imagine there are 80 developers working on a large project. They are using Continuous Integration pipelines in order to facilitate automated builds. We know buildincludes Unit Testing as well. One day they decided to deploy the latest build that had passed the unit tests into a test environment.This must be a lengthy but controlled approach to deployment that their environment specialists carried out. However, the system didnt seem to work.What Might Be The Obvious Cause Of The Failure?Well, the first reason that most of the people will think is that there is some problem with the configuration. Like most of the people even they thought so.They spent a lot of time trying to find what was wrong with the configuration of the environment, but they couldnt find the problem.One Perceptive Developer Took A Smart Approach:Then one of the senior Developer tried the application on his development machine. It didnt work there either.He stepped back through earlier and earlier versions until he found that the system had stopped working three weeks earlier. A tiny, obscure bug had prevented the system from s tarting correctly. Although, the project had good unit test coverage.Despite this, 80 developers, who usually only ran the tests rather than the application itself, did not see the problem for three weeks.Problem Statement:Without running Acceptance Tests in a production-like environment, they know nothing about whether the application meets the customers specifications, nor whether it can be deployed and survive in the real world. If they want timely feedback on these topics, they must extend the range of their continuous integration process.Let me summarize the lessons learned by looking at the above problems:Unit Tests only test a developers perspective of the solution to a problem. They have only a limited ability to prove that the application does what it is supposed to from a users perspective. They are not enough toidentify the real functional problems.Deploying the application on the test environment is a complex, manually intensive process that was quite prone to error.This meant that every attempt at deployment was a new experiment a manual, error-prone process.Solution Continuous Delivery Pipeline (Automated Acceptance Test):They took Continuous Integration (Continuous Delivery) to the next step and introduceda couple of simple, automated Acceptance Tests that proved that the application ran and could perform its most fundamental function.The majority of the tests running during the Acceptance Test stage are Functional Acceptance Tests.Basically, they built a Continuous Delivery pipeline, in order to make sure that the application is seamlessly deployed on the production environment, by making sure that the application works fine when deployed on the test server which is a replica of the production server.Enough of the theory, I will now show you how to create a Continuous Delivery pipeline using Jenkins.Continuous Delivery Pipeline Using Jenkins:Here I will be using Jenkins to create a Continuous Delivery Pipeline, which will include the followin g tasks:Steps involved in the Demo:Fetching the code from GitHubCompiling the source codeUnit testing and generating the JUnit test reportsPackaging the application into a WAR file and deploying it on the Tomcat serverPre-requisites:CentOS 7 MachineJenkins 2.121.1DockerTomcat 7Step 1 Compiling The Source Code:Lets begin by first creating a Freestyle project in Jenkins. Consider the below screenshot:Give a name to your project and select Freestyle Project:When you scroll down you will find an option to add source code repository, select git and add the repository URL, in that repository there is a pom.xml fine which we will use to build our project. Consider the below screenshot:Now we will add a Build Trigger. Pick the poll SCM option, basically, we will configure Jenkins to poll the GitHub repository after every 5 minutes for changes in the code. Consider the below screenshot:Before I proceed, let me give you a small introduction to the Maven Build Cycle.Each of the build lifecycl es is defined by a different list of build phases, wherein a build phase represents a stage in the lifecycle.Following is the list of build phases:validate validate the project is correct and all necessary information is availablecompile compile the source code of the projecttest test the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployedpackage take the compiled code and package it in its distributable format, such as a JAR.verify run any checks on results of integration tests to ensure quality criteria are metinstall install the package into the local repository, for use as a dependency in other projects locallydeploy done in the build environment, copies the final package to the remote repository for sharing with other developers and projects.I can run the below command, for compiling the source code, unit testing and even packaging the application in a war file:mvn clean packageYou can also break down you r build job into a number of build steps. This makes it easier to organize builds in clean, separate stages.So we will begin by compiling the source code. In the build tab, click on invoke top level maven targets and type the below command: compileConsider the below screenshot:This will pull the source code from theGitHub repository and will also compile it (Maven Compile Phase).Click on Save and run the project.Now, click on the console output to see the result.Step 2 Unit Testing:Now we will create one more Freestyle Project for unit testing. Add the same repository URL in the source code management tab, like we did in the previous job.Now, inthe BuidTrigger tab click on the build after other projects are built. There type the name of the previous project where we are compiling the source code, and you can select any of the below options:Trigger only if the build is stableTrigger even if the build is unstableTrigger even if the build failsI think the above options are pretty self -explanatory so, select any one. Consider the below screenshot:In the Build tab, click on invoke top level maven targets and use the below command:test Jenkinsalso does a great job of helping you display your test results and test result trends.Thede facto standard for test reporting in the Java world is anXML format used by JUnit.This format is also used by many other Java testing tools, such as TestNG, Spock, and Easyb. Jenkins understands this format, so if your build produces JUnit XML test results, Jenkins can generate nice graphical test reports and statistics on test results over time, and also let you view the details of any test failures. Jenkins also keeps track of how long your tests take to run, both globally, and per testthis can come in handy if you need to track down performance issues.So the next thing we need to do is to get Jenkins to keep tabs on our unit tests.Go to the Post-build Actions section and tick Publish JUnit test result report checkbox. When Maven runs unit tests in a project, it automatically generates the XML test reports in a directory called surefire-reports. So enter **/target/surefire-reports/*.x ml in the Test report XMLs field. The two asterisks at the start of the path (**) are a best practice to make the configuration a bit more robust: they allow Jenkins to find the target directory no matter how we have configured Jenkins to check out the source code.**/target/surefire-reports/*.xmlAgain save it and click on Build Now.Now, the JUnit report is written to /var/lib/jenkins/workspace/test/gameoflife-core/target/surefire-reports/TEST-behavior.In the Jenkins dashboardyou can also notice the test results:Step 3 Creating A WAR File And Deploying On The Tomcat Server:Now, the next step is to package our application in a WAR file and deploy that on the Tomcat server for User Acceptance test.Create one more freestyle project and add the source code repository URL.Then in the build trigger tab, select build when other projects are built, consider the below screenshot:Basically, after the test job, the deployment phase will start automatically.In the build tab, select shell script . Type the below command to package the application in a WAR file:mvn packageNext step is to deploy this WAR file to the Tomcat server. In the Post-Build Actions tab select deploy war/ear to a container. Here, give the path to the war file and give the context path. Consider the below screenshot:Select the Tomcat credentials and, notice the above screenshot. Also, you need to give the URL of your Tomcat server.In order to add credentials in Jenkins, click on credentials option on the Jenkins dashboard.Click on System and select global credentials.Then you will find an option to add the credentials. Click on it and add credentials.Add the Tomcat credentials, consider the below screenshot.Click onOK.Now in your Project Configuration, add the tomcat credentials which you have inserted in the previous step.Click on Save and then select Build Now.Go to your tomcat URL, with the context path, in my case it ishttp://localhost:8081. Now add the context path in the end, consider the below Sc reenshot:Link -http://localhost:8081/gofI hope you have understood the meaning of the context path.Now create a pipeline view, consider the below screenshot:Click on the plus icon, to create a new view.Configure the pipeline the way you want, consider the below screenshot:I did not change anything apart from selecting the initial job. So my pipeline will start from compile. Based on the way I have configured other jobs, after compile testing and deployment will happen.Finally, you can test the pipeline by clicking on RUN. After every five minutes, if there is a change in the source code, the entire pipeline will be executed.So we are able to continuously deploy our application on the test server for user acceptance test (UAT). I hope you have enjoyed reading this post on Continuous Delivery.If you have any doubts, feel free to put them in the comment section below and I will get back with an answer at the earliest. In Order To Build CI/ CD Pipelines You Need To Master Wide Variety O f Skills Master The Required DevOps Skills Now Recommended videos for you DevOps-Redefining your IT Strategy Watch Now What is Jenkins? Continuous Integration With Jenkins Watch Now What is Docker DevOps Tool For Containerization Watch Now DevOps is Going to Replace SDLC! Learn Why Watch Now DevOps Tutorial For Beginners Watch Now Puppet Tutorial DevOps Tool For Configuration Management Watch Now 5 Best Practices In DevOps Culture Watch Now Ansible Tutorial For Beginners Ansible Playbook Watch Now Top DevOps Interview Questions And Answers Watch Now What is DevOps A Beginners Guide To DevOps Watch Now What is Git A Complete Git Tutorial For Beginners Watch Now Continuous Integration With Jenkins Watch Now Devops : Automate Your Infrastructure With Puppet Watch NowRecommended blogs for you Why DevOps? 3 Ways In Which DevOps Improves Organizational Performance Read Article Top 10 DevOps Tools You Must Know In 2020 Read Article Top Chef Interview Questions All You Need To Know A bout Chef In 2020 Read Article Jenkins Master and Slave Architecture A Complete Guide Read Article What Is Agile Methodology Know the What and How? Read Article DevOps vs Agile! Everything You Need To Know Read Article Continuous Delivery Tutorial Building A Continuous Delivery Pipeline Using Jenkins Read Article Install Docker Docker Installation On Ubuntu And CentOS Read Article Gitting Ahead: Hacking Git and GitHub Part 2 Read Article Jenkins Pipeline Tutorial: A Beginners Guide To Continuous Delivery Read Article AWS Certified DevOps Engineer : A Perfect Amalgamation Read Article Azure Boards: How To Get Started With Agile Planning on Azure? Read Article Ansible for AWS Managing Cloud Made Easy Read Article What is Jenkins X and how is it Different from Jenkins? Read Article DevOps in various domains How DevOps solves the problem? Read Article How to use Puppet Modules for IT Infrastructure Automation? Read Article Install Git Git Installation On Windows And CentOS Read A rticle Git bisect: How to identify a bug in your code? Read Article Kubernetes Dashboard Installation and Views Read Article DevOps Roles: Which Of Them Is Your Dream? Read Article Comments 0 Comments Trending Courses in DevOps DevOps Certification Training72k Enrolled LearnersWeekend/WeekdayLive Class Reviews 5 (28700)