From 21130c3e8ea71b5c8b456dd6fb3e793bd6030845 Mon Sep 17 00:00:00 2001 From: Diego Araújo Date: Sun, 30 Jul 2017 11:31:58 -0300 Subject: [PATCH] [ieeeSW] Review Validation Environment Deployment --- ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index 1579cbe..1f1ef0c 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -157,11 +157,11 @@ the new packages would be ready to be used by our subsequent deployment scripts. The Validation Environment (VE) is a replica of the Production Environment (PE), with two exceptions: only the government officers and us had access to it -as well as all the data is anonymised. To configure the environment, we used +and all the data is anonymised. To configure the environment, we used our configuration management tool: Chake (serverless configuration with Chef). That maintained environment consistency simplifying the deployment process. -Additionally, the packages we built on the last step were readily available to -use by the management tool. +Additionally, the packages we built on the last step were readily available to be +used by the management tool. The VE was used by the government agents to validate new features and required changes. Also, the VE was useful to verify the integrity of the entire portal -- libgit2 0.21.2