Commit 83b8e0c54d4eafcdcc89e0fd9e696df201a433c5
1 parent
3efb263c
Exists in
master
and in
3 other branches
[ieeeSW] Grammarly on CD from Scratch section
Showing
1 changed file
with
4 additions
and
4 deletions
Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
| @@ -286,20 +286,20 @@ future works between industry and academia still need to address. | @@ -286,20 +286,20 @@ future works between industry and academia still need to address. | ||
| 286 | 286 | ||
| 287 | Taking on responsibilities for implementing CD impacted on the whole team. | 287 | Taking on responsibilities for implementing CD impacted on the whole team. |
| 288 | Our team did not have know-how in this approach, and we had few working hours | 288 | Our team did not have know-how in this approach, and we had few working hours |
| 289 | -available to allocate for the building of pipeline. The construction and | ||
| 290 | -maintenance of the CD process was possible by taking some decisions to mature | 289 | +available to allocate for the building of the pipeline. The construction and |
| 290 | +maintenance of the CD process were possible by taking some decisions to mature | ||
| 291 | the project: | 291 | the project: |
| 292 | 292 | ||
| 293 | 1. _Selecting the most experienced professionals and some developers of the | 293 | 1. _Selecting the most experienced professionals and some developers of the |
| 294 | project to work on a specific team for DevOps._ These professionals used their | 294 | project to work on a specific team for DevOps._ These professionals used their |
| 295 | -experiences in OSS projects to get an initial proposal of deployment process. | 295 | +experiences in OSS projects to get an initial proposal for the deployment process. |
| 296 | The solution enabled us to automate the deployment, even though the process was | 296 | The solution enabled us to automate the deployment, even though the process was |
| 297 | still rudimentary. | 297 | still rudimentary. |
| 298 | 298 | ||
| 299 | 2. _Interchanging team members and encouraging teammates to migrate to DevOps | 299 | 2. _Interchanging team members and encouraging teammates to migrate to DevOps |
| 300 | team._ The benefits of these movements were twofold: mitigating the difficulty | 300 | team._ The benefits of these movements were twofold: mitigating the difficulty |
| 301 | to pass the knowledge between DevOps developers and features developers, and | 301 | to pass the knowledge between DevOps developers and features developers, and |
| 302 | -evolving the process on-the-fly | 302 | +evolving the process on-the-fly. |
| 303 | 303 | ||
| 304 | Building a CD pipeline was hard in the beginning. We believe that more tools | 304 | Building a CD pipeline was hard in the beginning. We believe that more tools |
| 305 | to provide out-of-the-box standardized CD pipelines would be of great help for | 305 | to provide out-of-the-box standardized CD pipelines would be of great help for |