From e9c7510e9b72a640670a55a07c1274d8183fe8e3 Mon Sep 17 00:00:00 2001 From: Paulo Meirelles Date: Sun, 19 Nov 2017 19:51:15 -0200 Subject: [PATCH] [ieeeSW] Minor improvements --- ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 47 ++++++++++++++++++++++++----------------------- 1 file changed, 24 insertions(+), 23 deletions(-) diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index 2cbd6a4..910dc06 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -133,13 +133,14 @@ project, we became active participants in the deploy operations. ## Our Continuous Delivery Pipeline -SPB portal is a CDE with additional social features. We built system-of-systems -adapting and integrating five existing OSS projects: Colab -(www.github.com/colab), Noosfero (www.noosfero.org), Gitlab (www.gitlab.com), -Mezuro (www.mezuro.org), and Mailman (www.list.org). Colab orchestrates these -multiple components and allowed us to smoothly provide a unified interface for -final users, including single sign-on and global searches [1]. All these integrated -systems represents a total of 106.253 commits and 1.347.421 lines of code. +SPB portal is a CDE with additional social features, having 83 software +communities and 6,460 users. We built system-of-systems adapting and +integrating five existing OSS projects: Colab (www.github.com/colab), Noosfero +(www.noosfero.org), Gitlab (www.gitlab.com), Mezuro (www.mezuro.org), and +Mailman (www.list.org). Colab orchestrates these multiple components and +allowed us to smoothly provide a unified interface for final users, including +single sign-on and global searches [1]. All these integrated systems represents +a total of 106.253 commits and 1.347.421 lines of code. ![The SPB Deployment Pipeline.](figures/pipeline.png) @@ -174,14 +175,14 @@ this process, we started packaging. ### Packaging -After creating a new tag for a system, DevOps team starts the packaging process. -Packaging brings portability, simplifies deployment, and enables configuration -and permission control. Our packaging software approach involves building -separate packages for each system, in three steps: writing the script for the -specific environment, building the package, and uploading it to a package -repository. A set of scripts fully automated these steps. When all them ran -successfully, the new packages would be ready and available for our deployment -scripts. +After creating a new tag for a system, our DevOps team starts the packaging +process. Packaging brings portability, simplifies deployment, and enables +configuration and permission control. Our packaging software approach involves +building separate packages for each system, in three steps: writing the script +for the specific environment, building the package, and uploading it to a +package repository. A set of scripts fully automated these steps. When all them +ran successfully, the new packages would be ready and available for our +deployment scripts. ### Validation Environment Deployment @@ -196,17 +197,17 @@ simplifying the deployment process. After a new SPB portal deployment in the VE, we used the environment to verify the integrity of the entire portal. In this step, Ministry staff also checked -the new features, required changes, and bug fixes. If they identified a problem, -they would notify the developers via comments on the SPB portal issue tracker, -prompting the team to fix it and restart the pipeline. Otherwise, we could move -forward. +the new features, required changes, and bug fixes. If they identified a +problem, they would notify the developers via comments on the SPB portal issue +tracker, prompting the team to fix it and restart the pipeline. Otherwise, we +could move forward. ### Production Environment Deployment -After the VE check, we could finally begin the deployment in production, with the -same configuration management tool, scripts, and package versions as in the VE. -After the deploy was completed, both VE and PE were identical. At that point, -new features and bug fixes were finally available to end users. +After the VE check, we could finally begin the deployment in production, with +the same configuration management tool, scripts, and package versions as in the +VE. After the deploy was completed, both VE and PE were identical. At that +point, new features and bug fixes were finally available to end users. ## Benefits -- libgit2 0.21.2