... | ... | @@ -64,6 +64,10 @@ The first few blocks are written to: |
|
|
- Associate this GitLab pipeline with the Jenkins master job
|
|
|
- Create an `external job` for each stage specified and put them in a `pending` stage.
|
|
|
|
|
|
Stages are the following:
|
|
|
|
|
|
<img src="../images/enb-master-pipeline.png" alt="" border=3>
|
|
|
|
|
|
## 3.1. Verify Parameter stage ##
|
|
|
|
|
|
In this stage we are verifying if the parameters are consistent.
|
... | ... | @@ -100,3 +104,7 @@ Each variant build is performed in parallel on its corresponding VM. OAI build s |
|
|
|
|
|
Log files will be used to determine the pass/fail status of each build.
|
|
|
|
|
|
A dedicated VM performs static code analysis using the `cppcheck` tool.
|
|
|
At the time of writing, errors and warnings detected by this method are not a blocking stage.
|
|
|
|
|
|
When all variant builds, an HTML report is generated (like [this one](../documents/build_results.html)) and added to the job artifacts with all compilation logs. |
|
|
\ No newline at end of file |