... | ... | @@ -12,4 +12,33 @@ |
|
|
</tr>
|
|
|
</table>
|
|
|
|
|
|
## Table of Contents ## |
|
|
\ No newline at end of file |
|
|
## Table of Contents ##
|
|
|
|
|
|
1. [Introduction](#1-introduction)
|
|
|
2. [Source Control of the Jenkins pipeline script](#2-source-control-of-the-jenkins-pipeline-script)
|
|
|
3. [Declarative Pipeline Script](#3-declarative-pipeline-script)
|
|
|
4. [Python main script](#4-python-main-script)
|
|
|
5. [XML test case file](#5-xml-test-case-file)
|
|
|
|
|
|
# 1. Introduction #
|
|
|
|
|
|
Currently one of the slave jobs is hosted on the Eurecom Jenkins server at this [item/job](https://oailab.eurecom.fr:8083/jenkins/job/eNB-CI-FDD-Band7-B210/). This example tests the OAI eNB in FDD for Band7 with USRP 210 RF board.
|
|
|
|
|
|
This kind of slave jobs has no trigger. Only the eNB CI master triggers them within its Jenkins pipeline script. Nonetheless the master job SHALL provide the following parameters:
|
|
|
|
|
|
- **eNB_Repository** : a string that provides the GIT repository URL.
|
|
|
- **eNB_Branch** : a string that provides the GIT branch name.
|
|
|
- **eNB_CommitID** : a string that provides the SHA-0 commit ID.
|
|
|
- **eNB_mergeRequest** : a boolean that indicates if it was a merge request or a push event
|
|
|
|
|
|
Note that a slave job can be a standalone Jenkins, triggers by GitLab webhooks. See this template [job](https://oailab.eurecom.fr:8083/jenkins/job/CI-Sandbox-Ran/) for more details.
|
|
|
|
|
|
|
|
|
# 2. Source Control of the Jenkins pipeline script #
|
|
|
|
|
|
# 3. Declarative Pipeline Script #
|
|
|
|
|
|
# 4. Python main script #
|
|
|
|
|
|
# 5. XML test case file #
|
|
|
|