Continuous Integration & Continuous Deployment

Continuous Integration - CI

For our CI process, we used GitHub actions to run the build scripts and the testing scripts which were defined by our frontend and backend teams respectively. This is what we use to allow the merge to occur onto the master branch. If you pass all of the tests you can squash and merge your commits provided you have fulfilled all the other conditions to merge. We have implemented this system to ensure that new code doesn't break existing functionality.

Continuous Deployment - CD

When new code has been merged onto master we run two different build scripts, one to deploy the backend service and the second to deploy the frontend react app. This code is pushed onto two Azure App services, the frontend react app is found at ( https://doto.azurewebsites.net ) and the backend which serves our front end at ( https://doto-backend.azurewebsites.net ). In our deployed environment, the backend service connects to the production database ( Azure CosmosDB instance ) using connection strings which are stored securely as environment variables on in the backend config on Azure. More information about how the database connects can be found here.