diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index 5201f7a..60fe0c9 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -193,12 +193,14 @@ project, we became active participants in the deploy operations. ![Deployment Pipeline](figures/pipeline_3.png) -Figure 1 represents our CD pipeline. A new feature might require changes to -more than one SPB integrated software project. Notice that each one of them -could be modified independently. The pipeline started when new code arrived. As -it went through each step, it was tested and improved until it finally reached +Figure 1 represents our CD pipeline. It follows a typical deployment +pipeline[5], adapted to the technical and organizational context of our project +and the use of OSS projects practices. The pipeline started when a code arrived. +A new feature might require changes to more than one SPB integrated software +project. Notice that each one of them could be modified independently. As the +code went through each step, it was tested and improved until it finally reached the production environment. At this point, we would restart the pipeline to -release more new code. +release more versions. ### Automated Tests @@ -249,7 +251,7 @@ five reasons: * Packaging allows configurations and permissions control. After creating a new tag for one component, the developers informed our DevOps -[5] team, and the packaging process began. A set of scripts fully automated the +[6] team, and the packaging process began. A set of scripts fully automated the three packaging steps aforementioned. With all them running successfully, the new packages would be ready to be used by our deployment scripts. @@ -287,7 +289,7 @@ features and bug fixes were finally available to the end users. ## Benefits -Research points out many advantages of CD usage in the industry[2, 6], such as +Research points out many advantages of CD usage in the industry[2, 7], such as accelerated time to market, building the right product, productivity and efficiency improvements, stable releases, and better customer satisfaction. Working with the government, we noticed the following additional benefits. @@ -367,7 +369,7 @@ decisions to mature the project: 1. _Select the most experienced senior developers and some advanced software engineering students of the project to work on a specific team for DevOps._ These senior developers used their experiences in OSS projects to get an -initial proposal for the deployment process. The solution enabled us to +initial proposal for the deployment process. The solution enabled us to automate the deployment, even though the process was still rudimentary. 2. _Interchange team members and encouraging teammates to migrate to DevOps @@ -431,9 +433,9 @@ this article's reviewers. 2. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", IEEE Software, vol. 32, no. 2, 2015, pp. 50-54. 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. 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. -5. J. Davis and K. Daniels, "Effective Devops: Building a Culture of Collaboration, Affinity, and Tooling at Scale", O'Reilly Media, Inc., 2016. -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. -7. J. Humble and D. Farley, "Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation", Addison-Wesley Professional, 2010. +5. J. Humble and D. Farley, "Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation", Addison-Wesley Professional, 2010. +6. J. Davis and K. Daniels, "Effective Devops: Building a Culture of Collaboration, Affinity, and Tooling at Scale", O'Reilly Media, Inc., 2016. +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. -- libgit2 0.21.2