What is Continuous Integration (CI)?

Continuous integration means whenever new code is committed to remote repositories like GitHub, GitLab, etc. Continuous Integration (CI) will continuously build, tested, and merged into a shared repository.

How to Make a CI-CD Pipeline in Jenkins?

Pre-requisites: Jenkins

DevOps professionals mostly work with pipelines because pipelines can automate the processes like building, testing, and deploying the application. Doing manually by UI takes lots of time and effort which will affect productivity. With the help of  Continuous Integration / Continuous Deployment (CI/CD) Pipeline scripts we can automate the whole process which will increase productivity and save lots of time for the organization and can deliver quality applications to the end users.

Similar Reads

What is A CI/CD Pipeline?

CI/CD stands for Continuous Integration / Continuous Deployment first let us try to understand what is a pipeline. In computing, a pipeline is a set of stages or processes linked together to form a processing system. Each stage in the pipeline takes an input, processes it in accordance with a set of rules, and then sends the outputs to the stage that follows. Frequently, the pipeline’s overall output is its final step’s output. like the procedures outlined below...

What is Continuous Integration (CI)?

Continuous integration means whenever new code is committed to remote repositories like GitHub, GitLab, etc. Continuous Integration (CI) will continuously build, tested, and merged into a shared repository....

Benefits of Continuous Integration (CI)

We can maintain the reports of the projects Deployments can be made within the given time  Bugs can be found quickly....

Continuous Deployment/Delivery (CD)?

Continuous Deployment...

Sample Project – To Build A CI/CD Pipeline Using Jenkins

In this project, we will try to learn a basic CI/CD pipeline that is required to build a Java web application .war file by using Jenkins. To install Jenkins refers to the Jenkins installation....

Sample Pipelinescript To Deploy The Web Application Into The Tomcat Server

node { //Mention the tools which have been configured def mavenhome= tool name:"*****" // Mention how to trigger the Pipeline and how many Builds must be there and so on properties([buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '5', daysToKeepStr: ' ', numToKeepStr: '5')), pipelineTriggers([pollSCM('* * * * *')])]) // Getting the code from the GitHub stage('checkout code'){ git branch: 'development', credentialsId: '*******', url: '********' } //Building the code in to packages by using maven stage('build'){ sh "${mavenhome}/bin/mvn clean package" //Executing the code quality report by using SonarQube } stage('execute sonarqube package'){ sh "${mavenhome}/bin/mvn clean sonar:sonar" //Uploading the package into nexus } stage('upload buildartifact'){ sh "${mavenhome}/bin/mvn clean deploy" //Deploying th application into Tomcat } stage('tomcat'){ sshagent(['**********']) { sh "scp -o StrictHostKeyChecking=no target /maven-web-application.war ec2-user@*******:/opt/apache-tomcat-9.0.64/webapps/" } }...