Continuous Integration and Release pipelines

Why now? ADR-5 describes how we represent system configuration, but we need to decide how to build and maintain it

Scope: All software

Quality: Testability (current system configurations are needed for testing), reliability (critical for progressing system configuration)

Software configurations evolve quickly, especially while development is going on. Especially for the purpose of continuous integration we need to be able to automatically generate consistent system configurations that use the most current software versions available.

Similarly, the process of generating tagged versions (releases) needs to be automated. In contrast to continuous integration, this is not as much about speed, but we want the process to be reliable and well-exercised - and potentially connect up with continuous deployment processes as appropriate.