[ieeeSW] Chake URL

Paulo Meireles
1 parent ada57472
Showing 1 changed file with 5 additions and 5 deletions Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -258,11 +258,11 @@ new packages would be ready to be used by our deployment scripts.
 The Validation Environment (VE) is a replica of the Production Environment
 (PE), with two exceptions: only the government officers and project leaders had
 access to it and all the data became anonymous. To configure the environment,
-we used a configuration management tool named Chef with Chake support (a
-serverless configuration for Chef tool created by our team). It maintained
-environment consistency simplifying the deployment process.  Additionally, the
-packages we built on the last step were readily available to be used by the
-management tool.
+we used a configuration management tool named Chef with Chake support
+(www.github.com/terceiro/chake) -- a serverless configuration created by our
+team). It maintained environment consistency simplifying the deployment
+process.  Additionally, the packages we built on the last step were readily
+available to be used by the management tool.
  
 The MP agents used the VE to validate new features and required changes. The VE
 also was used to verify the integrity of the entire portal as part of the next
...	...	@@ -258,11 +258,11 @@ new packages would be ready to be used by our deployment scripts.
258	258	The Validation Environment (VE) is a replica of the Production Environment
259	259	(PE), with two exceptions: only the government officers and project leaders had
260	260	access to it and all the data became anonymous. To configure the environment,
261		-we used a configuration management tool named Chef with Chake support (a
262		-serverless configuration for Chef tool created by our team). It maintained
263		-environment consistency simplifying the deployment process. Additionally, the
264		-packages we built on the last step were readily available to be used by the
265		-management tool.
	261	+we used a configuration management tool named Chef with Chake support
	262	+(www.github.com/terceiro/chake) -- a serverless configuration created by our
	263	+team). It maintained environment consistency simplifying the deployment
	264	+process. Additionally, the packages we built on the last step were readily
	265	+available to be used by the management tool.
266	266
267	267	The MP agents used the VE to validate new features and required changes. The VE
268	268	also was used to verify the integrity of the entire portal as part of the next
...	...