Download as
Browse Code »

Commit 2a4624a99bb430c9a7d51f0f47e350ad3c5a02fe

Authored by Paulo Meireles
1 parent 2b94e087
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[ieeeSW] Shak is not Chake

Showing 1 changed file with 7 additions and 8 deletions   Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
  Diff comments   View file @2a4624a
@@ -81,13 +81,12 @@ quick response times to their requests which were, most of the time, influenced @@ -81,13 +81,12 @@ quick response times to their requests which were, most of the time, influenced
81 by the uncertainties of project continuity. We believed that would keep the 81 by the uncertainties of project continuity. We believed that would keep the
82 project alive even in a politically unstable and technically complex scenario. 82 project alive even in a politically unstable and technically complex scenario.
83 For that, during months we have worked to automate all the deploy process. For 83 For that, during months we have worked to automate all the deploy process. For
84 -instance, we have created a tool based on Chef called Shak (Self Hosting  
85 -Applications Kit) that offers an application installation interface based only  
86 - on instruction. It aims to make the deployment process easier for users  
87 - without technical knowledge, ensuring privacy and security for their Internet  
88 - applications. Thereby, we created a specific team dedicated to the deployment  
89 - process to mature our CD pipeline that would give us confidence to meet the  
90 - government’s requirements faster and faster. 84 +instance, one of our senior developers created a Chef server
  85 +(www.chef.io/chef) front-end tool called Chake (www.gitlab.com/terceiro/chake)
  86 +to help us to manage the multiple hosts needed for the project. In this
  87 +context, we created a specific team dedicated to the deployment process to
  88 +mature our CD pipeline that would give us confidence to meet the government’s
  89 +requirements faster and faster.
91 90
92 We describe our CD pipeline and how it speeded up our software delivery time. 91 We describe our CD pipeline and how it speeded up our software delivery time.
93 The CD made us adaptable for all requested changes and helped us to mitigate 92 The CD made us adaptable for all requested changes and helped us to mitigate
@@ -276,7 +275,7 @@ government, specially regarding CD. @@ -276,7 +275,7 @@ government, specially regarding CD.
276 275
277 ## References 276 ## References
278 277
279 -1. G. Booch, A. W. Brown, "Collaborative Development Environments, in Advances in Computers", vol. 59, 2003, pp. 1–27. 278 +1. G. Booch, A. W. Brown, "Collaborative Development Environments", in Advances in Computers, vol. 59, 2003, pp. 1–27.
280 1. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", in IEEE Software, vol. 32, no. 2, 2015, pp. 50-54. 279 1. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", in IEEE Software, vol. 32, no. 2, 2015, pp. 50-54.
281 1. P. Meirelles, M. Wen, A. Terceiro, R. Siqueira, L. Kanashiro, and H. Neri, "Brazilian Public Software Portal: an integrated platform for collaborative development", in Proceedings of the 13th International Symposium on Open Collaboration, 2017. 280 1. P. Meirelles, M. Wen, A. Terceiro, R. Siqueira, L. Kanashiro, and H. Neri, "Brazilian Public Software Portal: an integrated platform for collaborative development", in Proceedings of the 13th International Symposium on Open Collaboration, 2017.
282 281