summaryrefslogtreecommitdiff
path: root/ci-arch.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'ci-arch.mdwn')
-rw-r--r--ci-arch.mdwn25
1 files changed, 25 insertions, 0 deletions
diff --git a/ci-arch.mdwn b/ci-arch.mdwn
index 04a6327..c6773ad 100644
--- a/ci-arch.mdwn
+++ b/ci-arch.mdwn
@@ -68,6 +68,31 @@ Production here means all the software needed to run all the sites
supporting services, including tooling and services that supports
development.
+## Overall solution approach
+
+The overall approach to the architecture of the CI system, and the
+workflow supported by it, is to keep all changes in version control
+(git), which includes code, configuration, and scripts for building
+and deploying. When a change to version control is pushed, CI builds
+and tests the change, humans review the change, and if all seems to be
+in order, CI deploys to production.
+
+## Stakeholders
+
+Stakeholders in the WMF CI system include:
+
+* RelEng, who are responsible for keeping CI running
+* SRE, who are responsible for the infrastrcture on which CI runs
+* MediaWiki developers, who develop MW and its extensions, and will
+ (eventually) be doing MW releases for external MW deployers
+* staff and volunteer developers of anything else built, tested, and
+ deployed by CI
+* WMF, who pays for CI using donations
+* the Wikipedia movement, who use sites and services operated by WMF
+* all of humanity, who benefit from having knowledge freely
+ disseminated
+
+
# Requirements
This chapter lists the requirements we have for the CI system and