Add/change: document the internal CI components

This is somewhat speculative, as we don't know what the actual
implementation will be like, but rather than let the tool decide the
architecture, I'm trying to present an architecture that makes sense.

1 files changed, 6 insertions, 5 deletions

diff --git a/arch.dot b/arch.dot
index e998ea5..3c0aa60 100644
--- a/arch.dot
+++ b/arch.dot
@@ -5,7 +5,7 @@ digraph ci {
 
         controller [label="CI controller"];
         controller [shape="box"];
-        controller [fillcolor="grey" style="filled"];
+        controller [fillcolor="pink" style="filled"];
 
         vcs_worker [label="VCS worker"];
         vcs_worker [shape="ellipse"];
@@ -21,19 +21,19 @@ digraph ci {
 
         artifacts [label="artifact store"];
         artifacts [shape="cylinder"];
-        artifacts [fillcolor="grey" style="filled"];
+        artifacts [fillcolor="pink" style="filled"];
 
         logs [label="log store"];
         logs [shape="cylinder"];
-        logs [fillcolor="grey" style="filled"];
+        logs [fillcolor="pink" style="filled"];
 
         test_env [label="test\nenvironment"];
         test_env [shape="octagon"];
-        test_env [fillcolor="#0000ee" style="filled"];
+        test_env [fillcolor="grey" style="filled"];
 
         prod_env [label="production\nenvironment"];
         prod_env [shape="doubleoctagon"];
-        prod_env [fillcolor="red" style="filled"];
+        prod_env [fillcolor="white" style="filled"];
         
 
         gerrit -> controller;
@@ -45,6 +45,7 @@ digraph ci {
         artifacts -> build_worker;
         build_worker -> artifacts;
         build_worker -> logs;
+        build_worker -> test_env;
         vcs_worker -> logs;
         controller -> deployment_worker;
         artifacts -> deployment_worker;