Commit 5dce30fe04d367e1907475a37ac786dc72434bb4
1 parent
73598bf9
Exists in
master
and in
3 other branches
[i3eSW] Adding reference to CD pipeline
Showing
1 changed file
with
13 additions
and
11 deletions
Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
| ... | ... | @@ -193,12 +193,14 @@ project, we became active participants in the deploy operations. |
| 193 | 193 | |
| 194 | 194 |  |
| 195 | 195 | |
| 196 | -Figure 1 represents our CD pipeline. A new feature might require changes to | |
| 197 | -more than one SPB integrated software project. Notice that each one of them | |
| 198 | -could be modified independently. The pipeline started when new code arrived. As | |
| 199 | -it went through each step, it was tested and improved until it finally reached | |
| 196 | +Figure 1 represents our CD pipeline. It follows a typical deployment | |
| 197 | +pipeline[5], adapted to the technical and organizational context of our project | |
| 198 | +and the use of OSS projects practices. The pipeline started when a code arrived. | |
| 199 | +A new feature might require changes to more than one SPB integrated software | |
| 200 | +project. Notice that each one of them could be modified independently. As the | |
| 201 | +code went through each step, it was tested and improved until it finally reached | |
| 200 | 202 | the production environment. At this point, we would restart the pipeline to |
| 201 | -release more new code. | |
| 203 | +release more versions. | |
| 202 | 204 | |
| 203 | 205 | ### Automated Tests |
| 204 | 206 | |
| ... | ... | @@ -249,7 +251,7 @@ five reasons: |
| 249 | 251 | * Packaging allows configurations and permissions control. |
| 250 | 252 | |
| 251 | 253 | After creating a new tag for one component, the developers informed our DevOps |
| 252 | -[5] team, and the packaging process began. A set of scripts fully automated the | |
| 254 | +[6] team, and the packaging process began. A set of scripts fully automated the | |
| 253 | 255 | three packaging steps aforementioned. With all them running successfully, the |
| 254 | 256 | new packages would be ready to be used by our deployment scripts. |
| 255 | 257 | |
| ... | ... | @@ -287,7 +289,7 @@ features and bug fixes were finally available to the end users. |
| 287 | 289 | |
| 288 | 290 | ## Benefits |
| 289 | 291 | |
| 290 | -Research points out many advantages of CD usage in the industry[2, 6], such as | |
| 292 | +Research points out many advantages of CD usage in the industry[2, 7], such as | |
| 291 | 293 | accelerated time to market, building the right product, productivity and |
| 292 | 294 | efficiency improvements, stable releases, and better customer satisfaction. |
| 293 | 295 | Working with the government, we noticed the following additional benefits. |
| ... | ... | @@ -367,7 +369,7 @@ decisions to mature the project: |
| 367 | 369 | 1. _Select the most experienced senior developers and some advanced software |
| 368 | 370 | engineering students of the project to work on a specific team for DevOps._ |
| 369 | 371 | These senior developers used their experiences in OSS projects to get an |
| 370 | -initial proposal for the deployment process. The solution enabled us to | |
| 372 | +initial proposal for the deployment process. The solution enabled us to | |
| 371 | 373 | automate the deployment, even though the process was still rudimentary. |
| 372 | 374 | |
| 373 | 375 | 2. _Interchange team members and encouraging teammates to migrate to DevOps |
| ... | ... | @@ -431,9 +433,9 @@ this article's reviewers. |
| 431 | 433 | 2. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", IEEE Software, vol. 32, no. 2, 2015, pp. 50-54. |
| 432 | 434 | 3. C. B. Nielsen, P. G. Larsen, J. Fitzgerald, J. Woodcock, and J. Peleska, "Systems of Systems Engineering: Basic Concepts, Model-Based Techniques, and Research Directions", ACM Comput. Surv. 48, 2, Article 18, 2015, 41 pages. |
| 433 | 435 | 4. P .Meirelles, M. Wen, A. Terceiro, R. Siqueira, L. Kanashiro, and H. Neri, "Brazilian Public Software Portal: an integrated platform for collaborative development", Proceedings of the 13th International Symposium on Open Collaboration (OpenSym '17). ACM, Article 16, 2017, 10 pages. |
| 434 | -5. J. Davis and K. Daniels, "Effective Devops: Building a Culture of Collaboration, Affinity, and Tooling at Scale", O'Reilly Media, Inc., 2016. | |
| 435 | -6. T. Savor, M. Douglas, M. Gentili, L. Williams, K. Beck and M. Stumm, "Continuous Deployment at Facebook and OANDA", 2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-C), Austin, TX, 2016, pp. 21-30. | |
| 436 | -7. J. Humble and D. Farley, "Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation", Addison-Wesley Professional, 2010. | |
| 436 | +5. J. Humble and D. Farley, "Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation", Addison-Wesley Professional, 2010. | |
| 437 | +6. J. Davis and K. Daniels, "Effective Devops: Building a Culture of Collaboration, Affinity, and Tooling at Scale", O'Reilly Media, Inc., 2016. | |
| 438 | +7. T. Savor, M. Douglas, M. Gentili, L. Williams, K. Beck and M. Stumm, "Continuous Deployment at Facebook and OANDA", 2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-C), Austin, TX, 2016, pp. 21-30. | |
| 437 | 439 | <!--- |
| 438 | 440 | Está referência "8" tem só uma página mesmo: avaliar se precisamos usar mesmo. |
| 439 | 441 | --> | ... | ... |