What is CI/CD in DevOps?
a thread...
1. Definition
CI/CD stands for Continuous Integration - Continuous Delivery.
2. What is Continuous Integration?
In the Dev team, multiple developers work on different modules where daily code is committed.
Dev tests their part of the code but many times they don't do integration testing.
For this, they need other's code as well this is where CI comes.
CI process, integrates code from all team members, builds the project and runs integrations tests and unit tests on the project.
It saves time, and informs of any bugs in the early stage.
This process is completely automated there's less chance of human errors.
CI process is always connected with a code repository.
The moment someone merge their code in the repository. It starts the build.
At any given time, it gives the latest status of the repository for any possible errors.
3. Continuous Deployment
After the source code is merged, build & unit tested, it is time to deploy it on a QA server for QA testing.
Again this is a continuous process, which means the moment code is merged it will be deployed on server via CI/CD pipeline.
QA tests and reports for any bug.
That bug is fixed by Dev.
Code gets merged & deployed Instantly on server.
Instantly available to QA for further testing. Thanks to CI/CD pipeline!
This full process is completely automated & super fast.
4. How does it work?
Popular tools like Jenkins, Bamboo,etc are used to create a CI/CD pipeline.
For deploying code on each server, there is a separate pipeline which is connected to there respective repository.
For, eg: Separate pipelines for QA, Stage, Prod env.
5. Benefits:
Fully automated system with fewer human errors.
Saves time, and increases the efficiency of the team.
Feedback loop is more frequent between end-customer and the software development team.
Blends well with Agile and DevOps culture.
6. Conclusion
Various organizations use if differently based on their requirement.
Some only uses CI. Some only uses CD and some both.
Some company only uses CI/CD for QA env only, due to limited access to prod env or due to someother reasons.
That's it for now!
I hope you learned something new.
If you loved this then you might also like my previous thread on DevOps:
twitter.com/vikasrajputin/status/1533618177459900417
Small Announcement! š¢
I've opened my calendar for my audience and love to interact with you over 1:1 sessions on:
1. Career Guidance/Mentorship
2. Candid Talks
3. Content Creation
For more details visit:
calendly.com/vikasrajputin/101
Namaste I'm Vikas,
I write a thread every Mon, Wed & Fri
on Java, Javascript & Fullstack Development.
To read all my future threads follow @vikasrajputin