Process of deployment - psit4-lamas/PSIT4-LaMaS GitHub Wiki

• Status: accepted
• Deciders: Tram Anh Duong, Vanessa Haas, Markus Wüest, Martin Wädensweiler, Aleksandar Spasoale, David Kern
• Date: 2019-03-11

Context and Problem Statement

The team asked themself two questions?

• How can we automate our deployment process?
• What form of automatic deployment process do we use?

Considered Options

• Continuous Delivery
• Continuous Deployment

Decision Outcome

Chosen option: "Continuous Delivery", because comes out best (see below).

Pros and Cons of the Options

Continuous Delivery

• Good, because all team members can work on the developer branch.
• Good, because we could still control when we want to deploy to production.
• Bad, because we need two branches: "Develop" and "Production".

Continuous Deployment

• Good, because it would automatically deploy to production.
• Bad, because the test coverage must be nearly 100%.
• Bad, because we would need to use feature toggles to turn off incomplete features.
• Bad, because we could face system outages during deployment.