Updated Software Architecture Document (SAD) (markdown)

Patrick 2020-12-06 22:43:34 +01:00
parent 4913e9aa93
commit 4b67b27468

@ -92,4 +92,5 @@ n/a
We use Jenkins as CI/CD server. Our Jenkins instance fullfills two purposes: We use Jenkins as CI/CD server. Our Jenkins instance fullfills two purposes:
1. Every commit is automatically built by Jenkins. The build status is then sent back to GitHub. That way, we can easily see if a commit contains changes that brake the application and fix them before we merge a pull request. 1. Every commit is automatically built by Jenkins. The build status is then sent back to GitHub. That way, we can easily see if a commit contains changes that brake the application and fix them before we merge a pull request.
2. Once we merge a pull request to master, the project gets built and deployed to our Webserver by Jenkins automatically 2. Once we merge a pull request to master, the project gets built and deployed to our Webserver by Jenkins automatically
This way, we can assure that no breaking changes are deployed which would result in a website downtime. This way, we can assure that no breaking changes are deployed which would result in a website downtime.