Download as
Browse Code »

Commit 41e4a7a07e6a62fb286f371697a2a8b6bb3a3eeb

Authored by Rafael Reggiani Manzo
1 parent 852a846e
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[ieeeSW] Review packaging description 

Minor improvements to the text idea flow.
Showing 1 changed file with 13 additions and 10 deletions   Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
  Diff comments   View file @41e4a7a
... ... @@ -143,11 +143,13 @@ consequence, we had different tag values.
143 143  
144 144 ### Packaging
145 145  
146   -The SPB Portal platform is running under the CentOS GNU/Linux distribution.
147   -Basically, packaging a software for that distribution has three steps: (1)
148   -write the script for the specific environment (RPM), (2) build the package, and
149   -(3) upload it to a package repository. We chose to package our components for
150   -several reasons:
  146 +The platform is running on the CentOS 7 GNU/Linux distribution.
  147 +Basically, packaging a software for that distribution has three steps: write
  148 +the script for the specific environment (RPM); build the package; and upload
  149 +it to a package repository.
  150 +
  151 +We chose to create our own packages for each software component for several
  152 +reasons:
151 153 * Not all software was packaged by the community;
152 154 * And those that existed were outdated;
153 155 * Packaging makes it easy to manage the software on a given distribution;
... ... @@ -157,11 +159,12 @@ several reasons:
157 159  
158 160 After creating a new tag for one component, the DevOps team was notified and
159 161 packaging process began. In the normal case, the three packaging steps
160   -aforementioned are fully automated by a set of scripts. However, if the team
161   -reports to DevOps any eventual dependency change, the first step has to be
162   -manual. For instance, one system could start requiring another system to be
163   -initialized and that made necessary for someone to manually update the package
164   -script.
  162 +aforementioned were fully automated by a set of scripts.
  163 +
  164 +However, if the developers reported to DevOps any eventual dependency change,
  165 +the first packaging step had to be manual. For instance, suppose one system
  166 +starts requiring another system to be initialized first. That required the
  167 +DevOps to manually update the packaging script respective to these systems.
165 168  
166 169 After all these scripts have run successfully, the new packages would be ready
167 170 to use by our subsequent deployment scripts.
... ...