... | ... | @@ -88,14 +88,40 @@ Stages are the following: |
|
|
|
|
|
## 3.1. Verify Parameters stage ##
|
|
|
|
|
|
In this stage we are verifying if the parameters are consistent.
|
|
|
|
|
|
If they are missing or incorrect, the pipeline will stop at this stage.
|
|
|
|
|
|
## 3.2. Build and Test stage ##
|
|
|
|
|
|
This is the main stage of this pipeline.
|
|
|
|
|
|
The Jenkins script executes the `main.py` python script with all the credentials. This is a Jenkins feature that offuscates in the console log all logins/passwords used.
|
|
|
|
|
|
The python script plays all the tes-tcases defined in the XML file (parameter of the job).
|
|
|
|
|
|
If the python script fails during one of the test-cases, the Jenkins build job will fail but the following stages will be executed anyway.
|
|
|
|
|
|
## 3.3. Terminate stages ##
|
|
|
|
|
|
The Terminate stages are executed in parallel for time optimization reasons. Components (EPC, eNB, UE) could have been terminated inside the XML file. But in case of failure before the end of the test-case list, we terminate everything to leave the CI bench in an idle state for the next build.
|
|
|
|
|
|
Terminate stages are calls to the `main.py` script with a dedicated syntax.
|
|
|
|
|
|
## 3.4. Log Collection stages ##
|
|
|
|
|
|
The Log Collection stages are executed in parallel for time optimization reasons. At this step, all components should have been terminated. All the associated log files should be closed to writing. It should be safe to retrieve and archive them.
|
|
|
|
|
|
Log Collection stages are calls to the `main.py` script with a dedicated syntax.
|
|
|
|
|
|
Note that during the 'Build and Test' stage, the `main.py` script generates an HTML report. This report is personalized for the build and archived as an artifact.
|
|
|
|
|
|
## 3.5. Final Post block ##
|
|
|
|
|
|
Based on the optional **pipelineZipsConsoleLog** parameter, the pipeline retrieves the complete console log of the build, zips it and archives it. Currently at Eurecom, it is not done.
|
|
|
|
|
|
In case of build failure, we make sure again that all components are terminated to leave the CI bench in an idle state.
|
|
|
|
|
|
## 3.6. Artifacts list ##
|
|
|
|
|
|
<img src="../images/enb-slave-artifacts.png" alt="" border=3>
|
... | ... | |