summaryrefslogtreecommitdiff
path: root/ci-arch.html
diff options
context:
space:
mode:
Diffstat (limited to 'ci-arch.html')
-rw-r--r--ci-arch.html5
1 files changed, 3 insertions, 2 deletions
diff --git a/ci-arch.html b/ci-arch.html
index 056caea..f9a1e90 100644
--- a/ci-arch.html
+++ b/ci-arch.html
@@ -5,7 +5,7 @@
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<meta name="author" content="Lars Wirzenius, Release Enginering" />
- <title>Thoughts on future WMF CI architecture</title>
+ <title>Thoughts on WMF CI architecture</title>
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
@@ -15,7 +15,7 @@
</head>
<body>
<header>
-<h1 class="title">Thoughts on future WMF CI architecture</h1>
+<h1 class="title">Thoughts on WMF CI architecture</h1>
<p class="author">Lars Wirzenius, Release Enginering</p>
<p class="date">work in progress, first draft being written</p>
</header>
@@ -86,6 +86,7 @@
<h2 id="hard-requirements">Hard requirements</h2>
<p>These are not absolute requirements, and can be negotiated, but only to a minor degree.</p>
<ul>
+<li><p><strong>ROLLBACK</strong>: If a change is deployed to production and turns out to cause problems, it is easy and quick to revert the change.</p></li>
<li><p><strong>FAST</strong> Must be fast enough that it isn’t perceived as a bottleneck by developers. We will need a metric for this.</p>
<ul>
<li><strong>SHORTCYCLETIME</strong> Must enable us to have a short cycle time (from idea to running in production). CI is not the only thing that affects this, but it is an important factor. We probably need a metric for this.</li>