Commit 82ca6dc33cf3ad7faae384d84ec629394e590788
1 parent
7c45f408
Exists in
master
and in
3 other branches
[ieeeSW] minor improvements
Showing
1 changed file
with
11 additions
and
11 deletions
Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -74,25 +74,25 @@ Portal was composited from more than ten different software projects, | @@ -74,25 +74,25 @@ Portal was composited from more than ten different software projects, | ||
74 | generating a complex deploy process working on seven servers. | 74 | generating a complex deploy process working on seven servers. |
75 | 75 | ||
76 | Therefore, we realised that we needed to take control over the deployment | 76 | Therefore, we realised that we needed to take control over the deployment |
77 | -process. We would use CD as a mean to keep the government satisfied and provide | 77 | +process. We used CD as a mean to keep the government satisfied and provide |
78 | quick response times to their requests which were, most of the time, influenced | 78 | quick response times to their requests which were, most of the time, influenced |
79 | by the uncertainties of project continuity. We believed that would keep the | 79 | by the uncertainties of project continuity. We believed that would keep the |
80 | project alive even in a politically unstable and technically complex scenario. | 80 | project alive even in a politically unstable and technically complex scenario. |
81 | -For that, during months we have worked to automate all the deploy process. For | ||
82 | -instance, one of our senior developers created a Chef server | 81 | +For that, during months we worked to automate all the deploy process. For |
82 | +instance, one of our senior developers created a Chef-Server | ||
83 | (www.chef.io/chef) front-end tool called Chake (www.gitlab.com/terceiro/chake) | 83 | (www.chef.io/chef) front-end tool called Chake (www.gitlab.com/terceiro/chake) |
84 | to help us to manage the multiple hosts needed for the project. In this | 84 | to help us to manage the multiple hosts needed for the project. In this |
85 | -context, we created a specific team dedicated to the deployment process to | 85 | +context, we organized a specific team dedicated to the deployment process to |
86 | mature our CD pipeline that would give us confidence to meet the government’s | 86 | mature our CD pipeline that would give us confidence to meet the government’s |
87 | requirements faster and faster. | 87 | requirements faster and faster. |
88 | 88 | ||
89 | -We describe our CD pipeline and how it speeded up our software delivery time. | ||
90 | -The CD made us adaptable for all requested changes and helped us to mitigate | ||
91 | -those aforementioned political challenges besides the technical issues. Among | ||
92 | -CD’s known benefits[2], we also explain those that were the most important in | ||
93 | -the project scenario for us: improving customer satisfaction and making | ||
94 | -reliable releases. Both kept the project alive for more two years during the | ||
95 | -worst political crisis after the re-democratization in Brazil. | 89 | +Here, we describe our CD pipeline and how it speeded up our software delivery |
90 | +time. The CD made us adaptable for all requested changes and helped us to | ||
91 | +mitigate those aforementioned political challenges besides the technical | ||
92 | +issues. Among CD’s known benefits[2], we also explain those that were the most | ||
93 | +important in the project scenario for us: improving customer satisfaction and | ||
94 | +making reliable releases. Both kept the project alive for more two years during | ||
95 | +the worst political crisis after the re-democratization in Brazil. | ||
96 | 96 | ||
97 | ## Our Continuous Delivery Pipeline | 97 | ## Our Continuous Delivery Pipeline |
98 | 98 |