From cb0fe74ea96325ff2261503ae91feed938001958 Mon Sep 17 00:00:00 2001 From: Lars Wirzenius Date: Mon, 20 May 2019 19:32:46 +0300 Subject: Add: stage to deploy to production --- ci-arch.mdwn | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) (limited to 'ci-arch.mdwn') diff --git a/ci-arch.mdwn b/ci-arch.mdwn index bfe1393..9f656a6 100644 --- a/ci-arch.mdwn +++ b/ci-arch.mdwn @@ -624,8 +624,9 @@ CI will provide a default pipeline for all projects. Projects may use that or specify another one. The pipeline will be divided into several stages. Mandatory stages for -all changes and all projects are commit and acceptance stage. Other -stages may be added to specific changes projects as needed. +all changes and all projects are commit, acceptance stage, and +deployment to production. 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 @@ -707,6 +708,12 @@ The acceptance stage can take time. Developers are not expected to wait until it is finished before they move on to working on something else. +## Deployment to production + +If prior stages have passed successfully, and manual code review +("Gerrit CR:+2 vote") has approved the change, this stage deploys the +change to production. + ## Manual tests Testers may instruct CI to deploy any recent built set of artifacts to -- cgit v1.2.1