From 78a934c14698b23db401822710d4d08e37e2e42f Mon Sep 17 00:00:00 2001 From: Siqueira Date: Thu, 27 Jul 2017 22:27:48 -0300 Subject: [PATCH] Review pipeline --- ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 27 ++++++++++----------------- 1 file changed, 10 insertions(+), 17 deletions(-) diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index c382268..c8445e6 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -105,23 +105,16 @@ we get back to the first stage to release more new code. ### Automated tests -[//]: # (TODO - Rever a escrita desta ideia com mais calma) -[//]: # (TODO - Adicionar que as mudanças no Colab quebravam todos os plugins.) -[//]: # (https://www.linux.com/blog/learn/chapter/dev-ops/2017/7/devops-fundamentals-part-3-continuous-delivery-and-deployment) - -Each one of the Portal's software components had their own test suite which -the development teams were required to maintain and expand if possible. The -integration of all these software was based on a plugin architecture and, -again, each plugin with its test suite to ensure this level of the platform -stability. - -This two-level testing approach provided us the necessary speed and -the trust that each software and the whole platform stability. By first running -the software specific test suite we checked its stability and, if there was any -errors, the developers were warned and the execution of the plugins test suite -was not started. - -Only after all tests passed we move to the next step down the pipeline. +Each one of the Portal's software components had their own test suite. The +development teams were required to maintain and expand them if possible. The +communication of all these software was based on a plugin architecture. Testing +the plugins were our integration tests. Finally, all tests ran in each +component continuous integration environment. + +This two-level testing provided us with the necessary speed and trust that +guaranteed both component and platform stability. If any error was found, the +pipeline stopped and the developers were notified. Only after all tests passed +we moved to preparing the release. ### Preparing a new release -- libgit2 0.21.2