Skip to content

Latest commit

 

History

History
27 lines (23 loc) · 9.38 KB

CI&CD.md

File metadata and controls

27 lines (23 loc) · 9.38 KB
Raw

Continious Integration & Delivery, and deployments

Letschess makes use of CI to validate the quality of the software and CD for building stable versions of the application.

Continious Integration

All services make use of an CI pipeline which builds the application, validates that tests are not failing and searches for code smells of the application using SonarQube.

Quality controll table

Frontend: Build Test Quality gateTechnical DebtBugsDuplicated Lines (%)Lines of Code
Backend: Build_and_test_app Quality Gate StatusCoverageTechnical DebtBugsVulnerabilitiesLines of Code
UserService: Build_and_test_app Quality Gate Status CoverageTechnical DebtBugsVulnerabilitiesLines of Code
GameService: Build_and_test_app Quality Gate StatusCoverageTechnical DebtBugsVulnerabilitiesLines of Code
MatchmakingService: Build_and_test_app Quality Gate StatusCoverageTechnical DebtBugsVulnerabilitiesLines of Code

Continious Delivery

Frontend: Build Test https://hub.docker.com/repository/docker/sacation/letschess-front
Backend: Build_and_test_app https://hub.docker.com/repository/docker/sacation/letschess-backend
UserService: Build_and_test_app https://hub.docker.com/repository/docker/sacation/letschess-userservice
GameService: Build_and_test_app https://hub.docker.com/repository/docker/sacation/letschess-gameservice
MatchmakingService: Build_and_test_app https://hub.docker.com/repository/docker/sacation/letschess-matchmakingservice

The application gets delivered to the docker hub so that the application can be deployed with the most up to date version of the app which is throughly tested for stability.

Deployment

The current version of the application is deployed on the FHICT NetLab server, which is behind a VPN. If you're part of FHICT: connect to the vpn of seclab, and connect to the server environment using ssh: [email protected]