diff options
| -rw-r--r-- | ci-arch.mdwn | 14 | ||||
| -rw-r--r-- | ci-arch.pdf | bin | 285107 -> 285105 bytes |
2 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 diff --git a/ci-arch.pdf b/ci-arch.pdf Binary files differindex 4866384..3a6829a 100644 --- a/ci-arch.pdf +++ b/ci-arch.pdf |