Countinuous intergration and countinuous intergartion are becoming increasingly essential for any development team. A well set CI/CD pipeline not only speed's up the development process but also help's in automating quality checks. Let us look in depth on how to setup out first CI/CD pipeline and achieve best results.
Countinuous Integration, Continuous Delivery and Continuous Deployment
Continuous Integration is where developer's regularly integrate their work on development branch. Each integartion triggers a automatic code check for quality and unit testing for reliability.
This approach enable's development process to be frequently checked and issues to be highlighted early on in the development process at each release.
Countinous Delivery is when every new release is deployed on the development / quality assurance server's automatically.
This ensures that every release is deployable to production like environment.
Countinous Deployment goes one step further where every release is deployed on live production environment to the customer's after CI. If a release passes all the unit testing and quality checks it is deployed to production environment.
Jenkins is a open source automation server which can be easily used to create a CI/CD pipeline. Let's dive right into setting up jenkins and check some important configurations.
- Installing Jenkins
Follow the steps below for Ubuntu Debian-based distributions.
wget -q -O - https://pkg.jenkins.io/debian/jenkins.io.key | sudo apt-key add - sudo sh -c 'echo deb http://pkg.jenkins.io/debian-stable binary/ > /etc/apt/sources.list.d/jenkins.list' sudo apt-get update sudo apt-get install jenkins
- First boot setup
- Visit http://localhost:8080
- Use administrator password at /var/lib/jenkins/secrets/initialAdminPassword for unlocking jenkins
- Configure a proxy server and port
- Install the suggested plugins
Pipelines to kick start your project
Swagger Documentation with ReDoc
Subscribe to Tech Inertia
Get the latest posts delivered right to your inbox