Download as
Browse Code »

Commit e9c7510e9b72a640670a55a07c1274d8183fe8e3

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

[ieeeSW] Minor improvements

Showing 1 changed file with 24 additions and 23 deletions   Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
  Diff comments   View file @e9c7510
... ... @@ -133,13 +133,14 @@ project, we became active participants in the deploy operations.
133 133  
134 134 ## Our Continuous Delivery Pipeline
135 135  
136   -SPB portal is a CDE with additional social features. We built system-of-systems
137   -adapting and integrating five existing OSS projects: Colab
138   -(www.github.com/colab), Noosfero (www.noosfero.org), Gitlab (www.gitlab.com),
139   -Mezuro (www.mezuro.org), and Mailman (www.list.org). Colab orchestrates these
140   -multiple components and allowed us to smoothly provide a unified interface for
141   -final users, including single sign-on and global searches [1]. All these integrated
142   -systems represents a total of 106.253 commits and 1.347.421 lines of code.
  136 +SPB portal is a CDE with additional social features, having 83 software
  137 +communities and 6,460 users. We built system-of-systems adapting and
  138 +integrating five existing OSS projects: Colab (www.github.com/colab), Noosfero
  139 +(www.noosfero.org), Gitlab (www.gitlab.com), Mezuro (www.mezuro.org), and
  140 +Mailman (www.list.org). Colab orchestrates these multiple components and
  141 +allowed us to smoothly provide a unified interface for final users, including
  142 +single sign-on and global searches [1]. All these integrated systems represents
  143 +a total of 106.253 commits and 1.347.421 lines of code.
143 144  
144 145 ![The SPB Deployment Pipeline.](figures/pipeline.png)
145 146  
... ... @@ -174,14 +175,14 @@ this process, we started packaging.
174 175  
175 176 ### Packaging
176 177  
177   -After creating a new tag for a system, DevOps team starts the packaging process.
178   -Packaging brings portability, simplifies deployment, and enables configuration
179   -and permission control. Our packaging software approach involves building
180   -separate packages for each system, in three steps: writing the script for the
181   -specific environment, building the package, and uploading it to a package
182   -repository. A set of scripts fully automated these steps. When all them ran
183   -successfully, the new packages would be ready and available for our deployment
184   -scripts.
  178 +After creating a new tag for a system, our DevOps team starts the packaging
  179 +process. Packaging brings portability, simplifies deployment, and enables
  180 +configuration and permission control. Our packaging software approach involves
  181 +building separate packages for each system, in three steps: writing the script
  182 +for the specific environment, building the package, and uploading it to a
  183 +package repository. A set of scripts fully automated these steps. When all them
  184 +ran successfully, the new packages would be ready and available for our
  185 +deployment scripts.
185 186  
186 187 ### Validation Environment Deployment
187 188  
... ... @@ -196,17 +197,17 @@ simplifying the deployment process.
196 197  
197 198 After a new SPB portal deployment in the VE, we used the environment to verify
198 199 the integrity of the entire portal. In this step, Ministry staff also checked
199   -the new features, required changes, and bug fixes. If they identified a problem,
200   -they would notify the developers via comments on the SPB portal issue tracker,
201   -prompting the team to fix it and restart the pipeline. Otherwise, we could move
202   -forward.
  200 +the new features, required changes, and bug fixes. If they identified a
  201 +problem, they would notify the developers via comments on the SPB portal issue
  202 +tracker, prompting the team to fix it and restart the pipeline. Otherwise, we
  203 +could move forward.
203 204  
204 205 ### Production Environment Deployment
205 206  
206   -After the VE check, we could finally begin the deployment in production, with the
207   -same configuration management tool, scripts, and package versions as in the VE.
208   -After the deploy was completed, both VE and PE were identical. At that point,
209   -new features and bug fixes were finally available to end users.
  207 +After the VE check, we could finally begin the deployment in production, with
  208 +the same configuration management tool, scripts, and package versions as in the
  209 +VE. After the deploy was completed, both VE and PE were identical. At that
  210 +point, new features and bug fixes were finally available to end users.
210 211  
211 212 ## Benefits
212 213  
... ...