From 80f1c62aae6621d3da026f200828a8b443548e2d Mon Sep 17 00:00:00 2001 From: Lars Wirzenius Date: Mon, 6 May 2019 17:59:55 +0300 Subject: Change: make bullet points into paragraphs --- ci-arch.mdwn | 39 +++++++++++++++++++-------------------- 1 file changed, 19 insertions(+), 20 deletions(-) (limited to 'ci-arch.mdwn') diff --git a/ci-arch.mdwn b/ci-arch.mdwn index 4f2b70d..004544e 100644 --- a/ci-arch.mdwn +++ b/ci-arch.mdwn @@ -29,26 +29,25 @@ abstract: | # Introduction -* CI WG plans replacement of its current WMF CI system with one of - Argo, GitLab CI, Zuul v3. These were selected in the first phase of - the CI WG. - -* We aim to do "continuous deployment", not only "continous - integration" or "continuous delivery". The goal is to deploy changes - to production as often and as quickly as possible, without - compromising on the safety and security of the production - environment. - -* This document goes into more detail of how the new CI system should - work, without (yet) discussing which replacement is chosen. A - meta-level architecture if you wish. - -* It is assumed as of the writing of this document that future CI will - build on and deploy to containers orchestrated by Kubernetes. - -* An important change is that we aim to change things so that as much - as possible, all software deployments are to containers - orchestrated by Kubernetes +CI WG plans replacement of its current WMF CI system with one of Argo, +GitLab CI, Zuul v3. These were selected in the first phase of the CI +WG. + +We aim to do "continuous deployment", not only "continous integration" +or "continuous delivery". The goal is to deploy changes to production +as often and as quickly as possible, without compromising on the +safety and security of the production environment. + +This document goes into more detail of how the new CI system should +work, without (yet) discussing which replacement is chosen. A meta +architecture if you wish. + +It is assumed as of the writing of this document that future CI will +build on and deploy to containers orchestrated by Kubernetes. + +An important change is that we aim to change things so that as much as +possible, all software deployments are to containers orchestrated by +Kubernetes # Requirements -- cgit v1.2.1