summaryrefslogtreecommitdiff
path: root/ci-arch.mdwn
diff options
context:
space:
mode:
authorLars Wirzenius <lwirzenius@wikimedia.org>2019-05-07 16:25:17 +0300
committerLars Wirzenius <lwirzenius@wikimedia.org>2019-05-07 16:25:17 +0300
commitb0959390b7552efd4203a70b345aff4cf0a888a5 (patch)
tree0ace91258e286cd1f6ab23572e7c7d5628840cc5 /ci-arch.mdwn
parent7776b55b4da532710d1ba1792b87153051ac5417 (diff)
downloadwmf-ci-arch-b0959390b7552efd4203a70b345aff4cf0a888a5.tar.gz
Change: reformat para
Diffstat (limited to 'ci-arch.mdwn')
-rw-r--r--ci-arch.mdwn14
1 files changed, 7 insertions, 7 deletions
diff --git a/ci-arch.mdwn b/ci-arch.mdwn
index f20a30c..6d41e20 100644
--- a/ci-arch.mdwn
+++ b/ci-arch.mdwn
@@ -612,13 +612,13 @@ all changes and all projects are commit and acceptance stage. Other
stages may be added to specific changes projects as needed.
The goal is that if the commit and acceptance stages pass, the change
-is a candidate that can be deployed to production, unless the
-project is such that it needs (say) manual testing or other human
-decision for the production deployment decision. Likewise, if the
-component or the change is particularly security or performance
-sensitive, stages that check those aspects may be required. CI will
-have ways of indicating the required changes per component, and also
-per change. (It is unclear how this will be managed.)
+is a candidate that can be deployed to production, unless the project
+is such that it needs (say) manual testing or other human decision for
+the production deployment decision. Likewise, if the component or the
+change is particularly security or performance sensitive, stages that
+check those aspects may be required. CI will have ways of indicating
+the required changes per component, and also per change. (It is
+unclear how this will be managed.)
If the commit or acceptance stage fails, there is not production
candidate. The pipeline as a whole fails. Any artifacts built by the