... | ... | @@ -35,6 +35,8 @@ The eNB-CI master job is configured to start when: |
|
|
|
|
|
The last one allows developers to fix issues on their working branch when requested by CI administrator or integrators.
|
|
|
|
|
|
<img src="../images/jenkins-gitlab-trigger-conf.png" alt="" border=3>
|
|
|
|
|
|
The eNB-CI master job may be configured without any parameter. In that case no social media notifications (such as Slack, Mattermost, ...) is performed.
|
|
|
|
|
|
At time of writing, the eNB-CI master job hosted at Eurecom is using the following parameters:
|
... | ... | @@ -100,11 +102,17 @@ The created VMs are brand new systems with a minimal package configuration. |
|
|
|
|
|
## 3.4. Build stages ##
|
|
|
|
|
|
Each variant build is performed in parallel on its corresponding VM. OAI build script will install all the needed packages.
|
|
|
Each variant build is performed in parallel on its corresponding VM. OAI build script will install all the needed packages. Each stage should be surrounded with the `gitlabCommitStatus` keyword associated with the stage name.
|
|
|
|
|
|
- When entering the stage, the status on the external job on the GitLab pipeline will pass from `pending` to `running`.
|
|
|
|
|
|
Log files will be used to determine the pass/fail status of each build.
|
|
|
Log files will be used to determine the pass/fail status of each build.
|
|
|
|
|
|
- When entering the stage, the status on the external job on the GitLab pipeline will pass from `pending` to `pass` or `fail`.
|
|
|
|
|
|
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 |
|
|
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.
|
|
|
|
|
|
Also in case of a Merge-Request, a script is analysing if the contributor did not introduce new compilation warnings. In that case, a comment in the Merge-Request discussion is added with the list of impacted files. |
|
|
\ No newline at end of file |