CI/CD for the timetable management System using Jenkins

πHello, Hashnode community! I'm subbaramireddy, a passionate DevOps Engineer with a relentless commitment to optimizing software development workflows and infrastructure management. π Hands-on experience in the DevOps field, I've honed my skills in AWS cloud services, containerization, and CI/CD pipelines. As an AWS Certified Developer, I'm well-versed in leveraging cloud technologies to drive efficiency and innovation. π‘ I firmly believe in the power of continuous improvement. My journey began with an internship, where I immersed myself in the intricacies of DevOps, from deploying web applications to orchestrating containerized solutions. I've also delved into AWS CDK, enhancing security through RDS instance policies, and creating foundational infrastructure with precision. π My goal is to share insights, best practices, and the latest trends in the DevOps landscape. I'm excited to connect with like-minded professionals, engage in meaningful discussions, and learn from the diverse experiences of the Hashnode community. π Let's explore the ever-evolving world of DevOps together. Feel free to connect with me, ask questions, or share your own insights. Together, we can drive innovation and efficiency in the tech world!
prerequisites
TTMS Repository view
Open Jenkins using the Jenkins master IP with port 8080.Login with Admin credentials.

After logging into Jenkins, we can see the dashboard.

Enter the item name as ttms-pipeline. select the Pipeline option and click on OK.

In the configure page select the required things as follows. Jenkinsfile

ttms-pipeline has been created click on the Build Now option for Continuous Integration and Continuous Delivery.

we can view the List of Stages in the CI/CD.

Open the ttms application using the public IP of the Jenkins-agent address with port 80.

To set up the Continuous Deployment open the GitHub repository of ttms and click on settings.

In the Code and automation select the Webhooks.

In the Webhooks click on the Add webhook.

Copy the public IP address of the Jenkins-master node and append the URL with the /github-webhook/. select the Content type as application/json and select just the push event. Enable the Active and click on Add webhook.

In the webhooks, we can view the added webhook status.

Modify the code in the ttms repo and push it. Automatically the GitHub hook will trigger the changes to the Jenkins-agent.

we can view the pipeline process status. Which is automatically triggered by the GitHub webhook.

Open the ttms application with Jenkins-agent IP. we can see the changes in the application.

Thanks for reading! I hope you found this helpful and informative.
I'm always happy to connect with fellow tech enthusiasts and answer any questions you may have. Don't forget to follow me for more updates on tech, programming, and more.ππ
Follow me on LinkedIn to see interesting posts like this : ) Linkedin






