Commit 810c2a28c214a82844e6313feae98434efcfaf72
1 parent
99eebfed
Exists in
master
and in
3 other branches
adding some takeaways in challenges
Showing
1 changed file
with
25 additions
and
14 deletions
Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
| @@ -271,24 +271,35 @@ governmental nucleus and improved the interactions with our development team. | @@ -271,24 +271,35 @@ governmental nucleus and improved the interactions with our development team. | ||
| 271 | 271 | ||
| 272 | ## Challenges | 272 | ## Challenges |
| 273 | 273 | ||
| 274 | -We successfully built a CD pipeline. In the end, we took over the deployment | ||
| 275 | -process from the government. That allowed us to survive into an unstable | ||
| 276 | -political scenario. However, we recognize that many challenges still need to be | ||
| 277 | -addressed by the industry and academia together. | 274 | +Due to the successful built of the CD pipeline, we took over the deployment |
| 275 | +process from the government and kept the project alive in an unstable political | ||
| 276 | +scenario. However, we recognize that many challenges still need to be addressed | ||
| 277 | +by the industry and academia together. | ||
| 278 | 278 | ||
| 279 | ### Build CD From Scratch | 279 | ### Build CD From Scratch |
| 280 | 280 | ||
| 281 | -Taking on CD responsibilities had a significant impact on the team. We did not | ||
| 282 | -have the know-how and had little time to come up with a working pipeline. The | ||
| 283 | -senior developers were crucial at this point. They came up with an initial | ||
| 284 | -solution to get the team started. That already enabled us to automatize | ||
| 285 | -deployment, even though the process was still rudimentary. We had to evolve our | ||
| 286 | -solution on-the-fly. We dedicated a few developers to this task. | ||
| 287 | - | ||
| 288 | -Building a CD pipeline was hard in the beginning. More tools that provide | ||
| 289 | -out-of-the-box standardized CD pipelines would be of great help for | 281 | +Taking on responsibilities for implementing CD impacted on the organization and |
| 282 | +activities of the whole team. Our team did not have know-how in this approach | ||
| 283 | +and we had few working hours available to allocate to building a pipeline. The | ||
| 284 | +construction and maintenance of the CD process was possible by taking some | ||
| 285 | +decisions to mature the project: | ||
| 286 | +(i) Selecting the most experienced professionals and a few developers of the | ||
| 287 | +project to work on a small DevOps team. These professionals used their | ||
| 288 | +experiences in FLOSS projects to get an initial proposal of deployment process. | ||
| 289 | +The solution enabled us to automate the deployment, even though the process was | ||
| 290 | +still rudimentary. | ||
| 291 | +(ii) Interchanging team members and encouraging teammates to migrate to DevOps | ||
| 292 | +team. The benefits of these movements were twofold: mitigating the difficulty | ||
| 293 | +to pass the knowledge from developers who had already understood the CD to the | ||
| 294 | +others who were dedicated to the development of features of the platform, and | ||
| 295 | +evolving the process on-the-fly. | ||
| 296 | +% | ||
| 297 | +Building a CD pipeline was hard in the beginning. We believe that more tools | ||
| 298 | +to provide out-of-the-box standardized CD pipelines would be of great help for | ||
| 290 | inexperienced teams. Tools that track each step of the pipeline and organize | 299 | inexperienced teams. Tools that track each step of the pipeline and organize |
| 291 | -logs in a human-manageable way are necessary too. | 300 | +logs in a human-manageable way are necessary too. We also suggest further |
| 301 | +research on how to effectively spread knowledge across inexperienced developers | ||
| 302 | +in a high turnover scenario. | ||
| 292 | 303 | ||
| 293 | ### Handling Inexperienced Teams | 304 | ### Handling Inexperienced Teams |
| 294 | 305 |