https://github.com/saravanan81java/devops-springboot
Devops SpringBoot Jenkins cicd automation
https://github.com/saravanan81java/devops-springboot
Last synced: 3 months ago
JSON representation
Devops SpringBoot Jenkins cicd automation
- Host: GitHub
- URL: https://github.com/saravanan81java/devops-springboot
- Owner: saravanan81java
- Created: 2024-11-05T01:53:27.000Z (7 months ago)
- Default Branch: main
- Last Pushed: 2025-02-21T03:25:33.000Z (3 months ago)
- Last Synced: 2025-02-21T04:26:26.587Z (3 months ago)
- Language: Java
- Size: 15.6 MB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Devops Jenkins CI CD automation Springboot project
# Project Name
DevOps Spring Boot
## Technologies Used
- **Java 17** (for backend development)
- **Spring Boot** (for microservices)
- **React.js** (for frontend)
- **Docker** (for containerization)
- **Kubernetes** (for Container orchestration)
- **AWS Services** (for cloud deployment)
- **PostgreSQL** (for database)
## Description
This project demonstrates a sample Jenkins pipeline with multiple stages for deploying applications using Docker containerization. It includes automated build, test, and deployment steps to streamline the CI/CD process.
Explanation of Jenkins Pipeline Stages
**1. Checkout Stage**
- Clones the repository from GitHub.
- Ensures that the latest source code is pulled into Jenkins.
**2. Build Stage**
- Runs a Maven build (mvn clean package) to compile and package the application.
- Ensures the application is ready for deployment.
**3. Build Docker Image**
- Uses a Dockerfile to create an image of the application.
- Tags the image with a meaningful name (my-app:latest).
**4. Push to Docker Registry**
- Uses Jenkins credentials (docker-hub-credentials) to log in to Docker Hub.
- Pushes the newly built Docker image to a registry (my-docker-repo).
**5. Deploy Stage**
- Runs a container from the pushed Docker image.
- Exposes the application on port 8080.
## Additional Enhancements
- **Automated Testing:** Add a Test stage using JUnit or integration tests before deploying.
- **Environment Variables:** Store sensitive data in Jenkins credentials instead of hardcoding.
- **Notifications:** Add Slack/email notifications for success/failure.
- **Kubernetes Deployment:** Instead of docker run, you can deploy using Kubernetes (kubectl apply).
- Jenkin Stage View snipshot
- 