Continuous delivery

Principles of software delivery

  • create a repeatable, reliable process
  • automate almost everything
  • keep everything in version control
  • if it hurts, do it more frequently
  • build quality in
  • done means released
  • everybody is responsible for the delivery process

Deploying risks

  • break existing expected behaviours of the system
  • introduce new unexpected behaviours of the system
  • corrupt the data because of a scheme design mistake or failed migration
  • introduce performance problem

We need safety measures to prevent this. We have continuous delivery to increase the safety and speed of changes.

The rest of the content (8 read minutes) is restricted.

Please use your personal access token or register to access.

Create account or login