My DevOps Journey – Milestone 9: Continuous Integration with Jenkins

Hello everyone 👋

In this milestone of my DevOps + Cloud learning journey, I explored Continuous Integration (CI) and how to implement it using Jenkins.

CI helps detect issues early by building and testing code automatically whenever developers commit changes. Instead of waiting until the end of development, CI ensures problems are identified immediately.

I learned how Jenkins fits into the CI workflow. Jenkins connects with Git, fetches the latest code, builds it, runs tests, and provides feedback. Its plugin ecosystem makes it easy to integrate tools for build, testing, scanning, and deployment.

A major part of this milestone was understanding Jenkins Pipeline as Code, where the entire workflow is defined in a Jenkinsfile. This makes CI/CD more reliable, version-controlled, and consistent.

I also studied how Jenkins integrates with tools like SonarQube for code quality checks and Nexus for storing artifacts. The concept of master and agent nodes helped me understand how large teams run builds on multiple systems.

Finally, I learned how Jenkins jobs can be triggered automatically—using schedules, SCM polling, or even remotely through API tokens and curl requests.

Overall, this milestone helped me understand how modern software teams achieve faster, reliable, and automated integration.

I’ve documented everything clearly on my GitHub for reference.

github link:https://github.com/darshan090905/Devops-learning/blob/master/milestone-9/jenkins.md

#DevOps #Jenkins #CI #Automation #LearningInPublic