... | ... | @@ -112,11 +112,11 @@ The created VMs are brand new systems with a minimal package configuration. |
|
|
|
|
|
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` (<img src="../images/gitlab-pipeline-pending.png" alt="" border=3>) to `running` (<img src="../images/gitlab-pipeline-running.png" alt="" border=3>).
|
|
|
- When entering the stage, the status on the external job on the GitLab pipeline will pass from `pending` (<img src="../images/gitlab-pipeline-pending.png" alt="" border=3>) to `running` (<img src="../images/gitlab-pipeline-status-running.png" alt="" border=3 height=24 width=87>).
|
|
|
|
|
|
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 `running` (<img src="../images/gitlab-pipeline-running.png" alt="" border=3>) to `pass` or `fail` (<img src="../images/gitlab-pipeline-pass-fail.png" alt="" border=3>).
|
|
|
- When entering the stage, the status on the external job on the GitLab pipeline will pass from `running` (<img src="../images/gitlab-pipeline-status-running.png" alt="" border=3 height=24 width=87>) to `pass` or `fail` (<img src="../images/gitlab-pipeline-pass-fail.png" alt="" border=3>).
|
|
|
|
|
|
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.
|
... | ... | |