Download as
Browse Code »

Commit 68eb237cd534ca9ffea6fc17748adfba30287d93

Authored by Rodrigo Siqueira de Melo
1 parent 3a066990
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

Small fixes

Showing 1 changed file with 9 additions and 9 deletions   Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
  Diff comments   View file @68eb237
... ... @@ -107,7 +107,7 @@ As it went through each step, it was tested and improved until it finally reache
107 107 the production environment. At this point we got back to the first stage to release
108 108 more new code.
109 109  
110   -### Automated tests
  110 +### Automated Tests
111 111  
112 112 The SPB portal consists of more than 10 integrated software projects and each
113 113 of them, as well as the entire platform, had to be tested. These software
... ... @@ -124,7 +124,7 @@ by either a test error or coverage reduction below a certain threshold, the
124 124 pipeline stopped. Only when all tests pass, the pipeline proceed to the step of
125 125 preparing the release.
126 126  
127   -### Preparing a new release
  127 +### Preparing a New Release
128 128  
129 129 A SPB Portal release was composed of all its software components releases. Each
130 130 software component release was a git tag that referred to a specific feature or
... ... @@ -195,7 +195,7 @@ accelerated time to market, building the right product, productivity and
195 195 efficiency improvements, reliable releases and better customer satisfaction.
196 196 Working with the government, we noticed the following additional benefits.
197 197  
198   -### Responsiveness to change
  198 +### Responsiveness to Change
199 199  
200 200 Responsiveness was one of the direct benefits of adopting the CD pipeline. The
201 201 ability to react quickly to changes requested by the government was vital for
... ... @@ -213,7 +213,7 @@ way, we always had something to show on meetings, reducing anxiety to get the pl
213 213 project would last a little longer and they would not go looking for other
214 214 jobs.
215 215  
216   -### Shared responsibility
  216 +### Shared Responsibility
217 217  
218 218 Before the adoption of CD, the development team could not track what happened to the code
219 219 after its delivery, since government technicians were the only responsible
... ... @@ -229,7 +229,7 @@ Additionally, developers worked to improve the CD pipeline
229 229 to speed up the process of making available, in the production environment,
230 230 new features for the platform.
231 231  
232   -### Synchronicity between government and development
  232 +### Synchronicity Between Government and Development
233 233  
234 234 Despite the positive impacts that the CD pipeline brought to the project, its
235 235 implementation was not easy at first. The CD pipeline performance
... ... @@ -244,7 +244,7 @@ This problem was softened when the analysts realized the impact of
244 244 these delays on the final product and decided to allocate the revisions in its
245 245 work schedule and to request the access to production in time.
246 246  
247   -### Strengthening trust in work relationship with the government
  247 +### Strengthening Trust in Work Relationship with the Government
248 248  
249 249 Continuous delivery was also a tool that helped to strengthen trust in the
250 250 relationship between developers and government analysts, as well as between the
... ... @@ -268,7 +268,7 @@ process from the government. That allowed us to survive into an unstable
268 268 political scenario. However, we recognize that many challenges still need to be
269 269 addressed by the industry and academia together.
270 270  
271   -### Build CD from scratch
  271 +### Build CD From Scratch
272 272  
273 273 Taking on CD responsibilities had a significant impact on the team. We did not
274 274 have the know-how and had little time to come up with a working pipeline. The
... ... @@ -282,7 +282,7 @@ out-of-the-box standardized CD pipelines would be of great help for
282 282 inexperienced teams. Tools that track each step of the pipeline and organize
283 283 logs in a human-manageable way are necessary too.
284 284  
285   -### Handling inexperienced teams
  285 +### Handling Inexperienced Teams
286 286  
287 287 After the developers learned how CD worked, it was difficult to pass the
288 288 knowledge along to other teammates. We tried to mitigate this problem by
... ... @@ -290,7 +290,7 @@ encouraging members to migrate to the DevOps team. We suggest further research
290 290 on how to effectively spread knowledge across inexperienced developers in a high
291 291 turnover scenario.
292 292  
293   -### Overcoming mistrust
  293 +### Overcoming Mistrust
294 294  
295 295 In the project's beginning we struggled with deployment issues in the government
296 296 structure. We were in a paradoxical situation. The government demanded fast
... ...