Set up CI/CD pipeline

[ctrlaltkurt]

As part of a DevOps setup, we need to implement a CI/CD pipeline using Jenkins. The pipeline will ensure that the development team can build, test, and deploy code efficiently to AWS.

• [x] Determine the CPU, RAM, and disk requirements for the Jenkins EC2 server.
• [x] Set up Jenkins on an EC2 instance.
• [x] Install required plugins (GitHub Integration, Docker Pipeline, AWS integration).
• [x] Create Jenkinsfile for the CI/CD pipeline.
• [x] Containerize the backend using Docker.
• [x] Push the Docker image to AWS ECR.
• [x] Define ECS task resource allocation and autoscaling policies.
• [x] Deploy the containerized app to AWS EC2 or ECS.

[mehmeteyupoglu]

If you don't mind, let's keep all the configurations below the free tier limit because that will suffice for the scope of this project

[ctrlaltkurt]

CI/CD pipeline is complete. The setup includes two separate pipelines, one for the backend and one for the frontend. After merging code to the dev branch, we manually trigger the relevant Jenkins pipeline based on where the changes occurred. These jobs pull the code, build Docker images, push them to Amazon ECR, and deploy them on the application server (Amazon ec2) as containers.