diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index 4f92835..f2f185b 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -141,10 +141,24 @@ active participants in the deploy operations. ## Our Continuous Delivery Pipeline +The SPB portal is a system-of-systems with five integrated software projects. +Colab (www.github.com/colab), a systems integration platform for web +applications based on a plugin architecture, orchestrates communication +among them. For this, we had also to develop specific plugins for each portal +software component. + + +These software component have different levels of complexity and size. Colab +has had X commits which represent Y lines of code, Gitlab, 64.446 commits and +502.597 lines, Noosfero, 14.175 commits and 607.490 lines, Mezuro, 9.007 commits +and 217.828 lines, and, finally, Mailman with 19.101 commits and 180.871 lines. +We can thus realize, with only the sum of the integrated projects, we have a +platform that totals more than 106.729 commits and 1.508.786 lines of code. + ![The SPB Deployment Pipeline](figures/pipeline_3.png) Figure 1 presents our CD pipeline. It follows a typical deployment pipeline -[3], adapted to the technical and organizational context of our project and the +[3], adapted to the technical and organizational complexity of our project and the use of OSS best practices. The pipeline started when new 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 @@ -165,19 +179,9 @@ https://www.openhub.net/p/mailman ### Automated Tests - - -The SPB portal is a system-of-systems with 5 integrated software projects. Each -of them, as well as the entire platform, had to be tested. These software -components have their own test suite. Colab (www.github.com/colab), a systems -integration platform for web applications based on a plugin architecture, -orchestrates communication among them. Therefore, we developed specific plugins -for each portal software component, such as Gitlab (www.gitlab.com) and -Noosfero (www.noosfero.org). Each plugin also has its own test suite, working -also as integration tests. +As a software integration, the entire SPB platform, as well as each of its +components need to be tested. Futhermore, the plugins developed to integrate a +component has its own test suite, and this also work as integration tests. Both unit and integration tests provided us the performance and security needed to guarantee the stability of components and the platform. If any test suite -- libgit2 0.21.2