Commit 78a934c14698b23db401822710d4d08e37e2e42f

Authored by Rodrigo Siqueira de Melo
1 parent 38b11585

Review pipeline

ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -105,23 +105,16 @@ we get back to the first stage to release more new code. @@ -105,23 +105,16 @@ we get back to the first stage to release more new code.
105 105
106 ### Automated tests 106 ### Automated tests
107 107
108 -[//]: # (TODO - Rever a escrita desta ideia com mais calma)  
109 -[//]: # (TODO - Adicionar que as mudanças no Colab quebravam todos os plugins.)  
110 -[//]: # (https://www.linux.com/blog/learn/chapter/dev-ops/2017/7/devops-fundamentals-part-3-continuous-delivery-and-deployment)  
111 -  
112 -Each one of the Portal's software components had their own test suite which  
113 -the development teams were required to maintain and expand if possible. The  
114 -integration of all these software was based on a plugin architecture and,  
115 -again, each plugin with its test suite to ensure this level of the platform  
116 -stability.  
117 -  
118 -This two-level testing approach provided us the necessary speed and  
119 -the trust that each software and the whole platform stability. By first running  
120 -the software specific test suite we checked its stability and, if there was any  
121 -errors, the developers were warned and the execution of the plugins test suite  
122 -was not started.  
123 -  
124 -Only after all tests passed we move to the next step down the pipeline. 108 +Each one of the Portal's software components had their own test suite. The
  109 +development teams were required to maintain and expand them if possible. The
  110 +communication of all these software was based on a plugin architecture. Testing
  111 +the plugins were our integration tests. Finally, all tests ran in each
  112 +component continuous integration environment.
  113 +
  114 +This two-level testing provided us with the necessary speed and trust that
  115 +guaranteed both component and platform stability. If any error was found, the
  116 +pipeline stopped and the developers were notified. Only after all tests passed
  117 +we moved to preparing the release.
125 118
126 ### Preparing a new release 119 ### Preparing a new release
127 120