From 82ca6dc33cf3ad7faae384d84ec629394e590788 Mon Sep 17 00:00:00 2001 From: Paulo Meirelles Date: Thu, 27 Jul 2017 20:42:17 -0300 Subject: [PATCH] [ieeeSW] minor improvements --- ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index bb9f024..cf071fa 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -74,25 +74,25 @@ Portal was composited from more than ten different software projects, generating a complex deploy process working on seven servers. Therefore, we realised that we needed to take control over the deployment -process. We would use CD as a mean to keep the government satisfied and provide +process. We used CD as a mean to keep the government satisfied and provide quick response times to their requests which were, most of the time, influenced by the uncertainties of project continuity. We believed that would keep the project alive even in a politically unstable and technically complex scenario. -For that, during months we have worked to automate all the deploy process. For -instance, one of our senior developers created a Chef server +For that, during months we worked to automate all the deploy process. For +instance, one of our senior developers created a Chef-Server (www.chef.io/chef) front-end tool called Chake (www.gitlab.com/terceiro/chake) to help us to manage the multiple hosts needed for the project. In this -context, we created a specific team dedicated to the deployment process to +context, we organized a specific team dedicated to the deployment process to mature our CD pipeline that would give us confidence to meet the government’s requirements faster and faster. -We describe our CD pipeline and how it speeded up our software delivery time. -The CD made us adaptable for all requested changes and helped us to mitigate -those aforementioned political challenges besides the technical issues. Among -CD’s known benefits[2], we also explain those that were the most important in -the project scenario for us: improving customer satisfaction and making -reliable releases. Both kept the project alive for more two years during the -worst political crisis after the re-democratization in Brazil. +Here, we describe our CD pipeline and how it speeded up our software delivery +time. The CD made us adaptable for all requested changes and helped us to +mitigate those aforementioned political challenges besides the technical +issues. Among CD’s known benefits[2], we also explain those that were the most +important in the project scenario for us: improving customer satisfaction and +making reliable releases. Both kept the project alive for more two years during +the worst political crisis after the re-democratization in Brazil. ## Our Continuous Delivery Pipeline -- libgit2 0.21.2