Commit 38b115855471e8ac0b3b9aa4959196fac1f64a4a
1 parent
8595b27f
Exists in
master
and in
3 other branches
Finished challenges
Showing
1 changed file
with
26 additions
and
30 deletions
Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
| ... | ... | @@ -231,53 +231,49 @@ constantly updated the VE based on their feedback. This made our relation |
| 231 | 231 | strong and in moments that needed quick action they would rather give us access |
| 232 | 232 | to production. |
| 233 | 233 | |
| 234 | - | |
| 235 | 234 | ## Challenges |
| 236 | 235 | |
| 237 | 236 | We successfully built a functional CD pipeline. In the end, we took over the |
| 238 | 237 | deployment process from the government. That allowed us to survive into an |
| 239 | -unstable political scenario. However, we recognized that many challenges still | |
| 240 | -need to be addressed by the industry and academia together. Build CD from | |
| 241 | -scratch | |
| 242 | - | |
| 243 | -Taking on CD responsibilities had a significant impact on the team. We did not | |
| 244 | -have the know-how and had little time to come up with a working pipeline. To | |
| 245 | -make things worse, we were not aware of how companies normally organized their | |
| 246 | -teams to make CD feasible. | |
| 238 | +unstable political scenario. However, we recognize that many challenges still | |
| 239 | +need to be addressed by the industry and academia together. | |
| 247 | 240 | |
| 248 | -[//]: # (TODO - Deixar uma abertura para uma eventual pesquisa) | |
| 241 | +### Build CD from scratch | |
| 249 | 242 | |
| 250 | -The seniors were crucial at this point. They came up with an initial solution | |
| 251 | -to get us started. That already enabled us to automatize the deploy, even | |
| 252 | -though the process was still rudimentary. We had to evolve our solution | |
| 253 | -on-the-fly. We dedicated a few developers to this task. | |
| 243 | +Taking on CD responsibilities had a significant impact on the team. We did not | |
| 244 | +have the know-how and had little time to come up with a working pipeline. The | |
| 245 | +seniors were crucial at this point. They came up with an initial solution to | |
| 246 | +get us started. That already enabled us to automatize the deploy, even though | |
| 247 | +the process was still rudimentary. We had to evolve our solution on-the-fly. We | |
| 248 | +dedicated a few developers to this task. | |
| 249 | + | |
| 250 | +Building a CD pipeline was hard in the beginning, and we succeed thanks to the | |
| 251 | +seniors experience. We believe that more tools that provide out-of-the-box | |
| 252 | +standardized CD pipelines would be of great help for inexperienced teams. Tools | |
| 253 | +that track each step of the pipeline and organize logs in a human-manageable | |
| 254 | +way are necessary too. | |
| 254 | 255 | |
| 255 | 256 | ### Handling inexperienced teams |
| 256 | 257 | |
| 257 | 258 | After the developers learned how CD worked, it was difficult to pass the |
| 258 | 259 | knowledge along to other teammates. We tried to mitigate this by encouraging a |
| 259 | 260 | member's migration to the DevOps team. Further research on how to effectively |
| 260 | -spread knowledge across inexperienced developers in a scenario with a high | |
| 261 | -turnover are needed. | |
| 261 | +spread knowledge across inexperienced developers in a high turnover scenario | |
| 262 | +are needed. | |
| 262 | 263 | |
| 263 | -[//]: # (TODO - Refazer título abaixo - ideias: overcoming the challenges / overcoming the mistrust) | |
| 264 | - | |
| 265 | -### Building trust | |
| 266 | - | |
| 267 | -[//]: # (TODO - Deixar claro que government = os técnicos , análista ou agentes do governo, conforme for padronizado no texto) | |
| 264 | +### Overcoming mistrust | |
| 268 | 265 | |
| 269 | 266 | In the project’s first half we struggled with deploy related problems in the |
| 270 | 267 | government structure. We were in a paradoxical situation. The government |
| 271 | 268 | demanded speedy deliveries but would not give access to their production |
| 272 | -infrastructure. As an example, only in a very specific situation the government | |
| 273 | -allowed us to access the PE. After some interactions with the government we | |
| 274 | -convinced them to create the VE as an isolated replica of the PE in their own | |
| 275 | -infrastructure. The government agents then realized that it could be good for | |
| 276 | -the project if they granted us access to part of the structure since we could | |
| 277 | -deliver new features to them faster. We believe it is required more research on | |
| 278 | -development protocols and policies to improve the relation between industry and | |
| 279 | -government, specially regarding CD. | |
| 280 | - | |
| 269 | +infrastructure. As an example, only in specific situations the government | |
| 270 | +allowed us to access the PE. It took some interactions with government agents | |
| 271 | +before we convinced them to create the VE as an isolated replica of the PE in | |
| 272 | +their own infrastructure. The government agents then realized that it could be | |
| 273 | +beneficial for the project if they granted us access to part of the structure. | |
| 274 | +We believe it is required more research on development protocols and policies | |
| 275 | +to improve the relation between industry and government, specially regarding | |
| 276 | +CD. | |
| 281 | 277 | |
| 282 | 278 | ## References |
| 283 | 279 | ... | ... |