SuccessConsole Output

Started by GitLab push by Laurent Velez
Obtained Jenkinsfile.mec from git git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on build3.forge.etsi.org in /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-012-pipeline
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
using credential f9a9fd70-ea8b-4872-a9d5-d1fb1cf8123e
Cloning the remote Git repository
Cloning repository git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git
 > git init /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-012-pipeline # timeout=10
Fetching upstream changes from git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git +refs/heads/*:refs/remotes/origin/*
skipping resolution of commit remotes/origin/master, since it originates from another repository
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision fe946f61cf4bd9fe98fecb3b354ab5a44592df04 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f fe946f61cf4bd9fe98fecb3b354ab5a44592df04
Commit message: "Update cli-validate-openapis-mec.sh"
 > git rev-list --no-walk fe946f61cf4bd9fe98fecb3b354ab5a44592df04 # timeout=10
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] gitlabBuilds
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Resolve)
[Pipeline] sh
+ echo Resolve stage
Resolve stage
[Pipeline] updateGitlabCommitStatus
[Pipeline] dir
Running in /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-012-pipeline/apis
[Pipeline] {
[Pipeline] checkout
using credential f9a9fd70-ea8b-4872-a9d5-d1fb1cf8123e
Cloning the remote Git repository
Cloning repository git@forge.etsi.org:mec/gs012-rnis-api.git
 > git init /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-012-pipeline/apis # timeout=10
Fetching upstream changes from git@forge.etsi.org:mec/gs012-rnis-api.git
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:mec/gs012-rnis-api.git +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url git@forge.etsi.org:mec/gs012-rnis-api.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url git@forge.etsi.org:mec/gs012-rnis-api.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:mec/gs012-rnis-api.git
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:mec/gs012-rnis-api.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse remotes/origin/master^{commit} # timeout=10
 > git branch -a -v --no-abbrev --contains 68ced0cb6db0ddf635a3e8497c688e3dfbcc9246 # timeout=10
Checking out Revision 68ced0cb6db0ddf635a3e8497c688e3dfbcc9246 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 68ced0cb6db0ddf635a3e8497c688e3dfbcc9246
Commit message: "Update README.md"
 > git rev-list --no-walk e9b6a4ef50272d2c72b2de9339a343efee0e7e29 # timeout=10
[Pipeline] }
[Pipeline] // dir
[Pipeline] dir
Running in /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-012-pipeline/scripts
[Pipeline] {
[Pipeline] checkout
using credential f9a9fd70-ea8b-4872-a9d5-d1fb1cf8123e
Cloning the remote Git repository
Cloning repository git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git
 > git init /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-012-pipeline/scripts # timeout=10
Fetching upstream changes from git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git +refs/heads/*:refs/remotes/origin/*
skipping resolution of commit remotes/origin/master, since it originates from another repository
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision fe946f61cf4bd9fe98fecb3b354ab5a44592df04 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f fe946f61cf4bd9fe98fecb3b354ab5a44592df04
Commit message: "Update cli-validate-openapis-mec.sh"
[Pipeline] updateGitlabCommitStatus
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Validate)
[Pipeline] updateGitlabCommitStatus
[Pipeline] sh
+ echo Validate stage
Validate stage
[Pipeline] sh
+ bash ./scripts/cli-validate-openapis-mec.sh ./apis

------ Switching to ./apis folder --------
------ Checking for previous logs ------
Using dockerized validator (etsiforge/swagger-cli:4.0.3)
4.0.3: Pulling from etsiforge/swagger-cli
Digest: sha256:c6987d82d33715ec65ac79532768eb98152d83ed969754aa7f4a9344aea32d9a
Status: Image is up to date for etsiforge/swagger-cli:4.0.3
docker.io/etsiforge/swagger-cli:4.0.3

------ Validating all YAML files (may takes several minutes) ------

-- Final validator returns 0.
No errors found, all files validate the OpenAPI definition. Below the complete log.

---- Complete log of validation ----
---- Validating ./RniAPI.json: No configurations were defined in extends -- using built in recommended configuration by default. validating s/RniAPI.json... [1] ../specs/RniAPI.json:23:11 at #/tags/0/description Tag object should contain `description` field. 21 | "url": "https://localhost/rni/v2" 22 | }], 23 | "tags": [{ | ^ 24 | "name": "rni" | ^^^^^^^^^^^^^^^ 25 | }], | ^^ 26 | "paths": { 27 | "/queries/rab_info": { Warning was generated by the tag-description rule. [2] ../specs/RniAPI.json:1528:9 at #/paths/~1subscriptions/post/callbacks/notification/{$request.body#~1notificationSubscription.callbackReference}/post/responses Operation must have at least one `4xx` response. 1526 | } 1527 | }, 1528 | "responses": { | ^^^^^^^^^^^ 1529 | "204": { 1530 | "description": "No content" Warning was generated by the operation-4xx-response rule. s/RniAPI.json: validated in 305ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 2 warnings.
---- Validating ./RniAPI.yaml: No configurations were defined in extends -- using built in recommended configuration by default. validating s/RniAPI.yaml... [1] ../specs/RniAPI.yaml:20:3 at #/tags/0/description Tag object should contain `description` field. 18 | 19 | tags: 20 | - name: rni | ^^^^^^^^^ 21 | paths: 22 | /queries/rab_info: Warning was generated by the tag-description rule. [2] ../specs/RniAPI.yaml:1036:15 at #/paths/~1subscriptions/post/callbacks/notification/{$request.body#~1notificationSubscription.callbackReference}/post/responses Operation must have at least one `4xx` response. 1034 | mcc: '001' 1035 | cellId: 'FEDCBAA' 1036 | responses: | ^^^^^^^^^ 1037 | '204': 1038 | description: "No content" Warning was generated by the operation-4xx-response rule. s/RniAPI.yaml: validated in 308ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 2 warnings.


------ Content of the folder ------
LICENSE
openapi-validation.log
proto3
proto3-gen.md
README.md
RniAPI.json
RniAPI.yaml
[Pipeline] updateGitlabCommitStatus
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // gitlabBuilds
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS