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-015-pipeline [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Checkout SCM) [Pipeline] checkout using credential f9a9fd70-ea8b-4872-a9d5-d1fb1cf8123e > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > 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 > 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/* 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-015-pipeline/apis [Pipeline] { [Pipeline] checkout using credential f9a9fd70-ea8b-4872-a9d5-d1fb1cf8123e > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url git@forge.etsi.org:mec/gs015-bandwith-mgmt-api.git # timeout=10 Fetching upstream changes from git@forge.etsi.org:mec/gs015-bandwith-mgmt-api.git > git --version # timeout=10 using GIT_SSH to set credentials > git fetch --tags --progress git@forge.etsi.org:mec/gs015-bandwith-mgmt-api.git +refs/heads/*:refs/remotes/origin/* > git rev-parse remotes/origin/master^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains 5cd9cdca5b7cb280a152908ec46b3e57426092fd # timeout=10 Checking out Revision 5cd9cdca5b7cb280a152908ec46b3e57426092fd (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 5cd9cdca5b7cb280a152908ec46b3e57426092fd Commit message: "Merge branch 'stf606-final' into 'master'" > git rev-list --no-walk df45e254c784aadf7a53279f9c302bba04a6abbd # timeout=10 [Pipeline] } [Pipeline] // dir [Pipeline] dir Running in /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-015-pipeline/scripts [Pipeline] { [Pipeline] checkout using credential f9a9fd70-ea8b-4872-a9d5-d1fb1cf8123e > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > 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 > 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/* 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 ------ Found previous log. Removing it 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 ./BwManagementApi.json: No configurations were defined in extends -- using built in recommended configuration by default. validating s/BwManagementApi.json... [1] ../specs/BwManagementApi.json:25:5 at #/tags/0/description Tag object should contain `description` field. 23 | ], 24 | "tags": [ 25 | { | ^ 26 | "name": "bwm" | ^^^^^^^^^^^^^ 27 | } | ^ 28 | ], 29 | "paths": { Warning was generated by the tag-description rule. s/BwManagementApi.json: validated in 107ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 1 warning. ---- Validating ./TrafficSteeringApi.json: No configurations were defined in extends -- using built in recommended configuration by default. validating s/TrafficSteeringApi.json... [1] ../specs/TrafficSteeringApi.json:25:5 at #/tags/0/description Tag object should contain `description` field. 23 | ], 24 | "tags": [ 25 | { | ^ 26 | "name": "mts" | ^^^^^^^^^^^^^ 27 | } | ^ 28 | ], 29 | "paths": { Warning was generated by the tag-description rule. s/TrafficSteeringApi.json: validated in 91ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 1 warning. ---- Validating ./BwManagementApi.yaml: No configurations were defined in extends -- using built in recommended configuration by default. validating s/BwManagementApi.yaml... [1] ../specs/BwManagementApi.yaml:20:3 at #/tags/0/description Tag object should contain `description` field. 18 | 19 | tags: 20 | - name: "bwm" | ^^^^^^^^^^^ 21 | 22 | paths: Warning was generated by the tag-description rule. s/BwManagementApi.yaml: validated in 105ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 1 warning. ---- Validating ./TrafficSteeringApi.yaml: No configurations were defined in extends -- using built in recommended configuration by default. validating s/TrafficSteeringApi.yaml... [1] ../specs/TrafficSteeringApi.yaml:20:3 at #/tags/0/description Tag object should contain `description` field. 18 | 19 | tags: 20 | - name: "mts" | ^^^^^^^^^^^ 21 | 22 | paths: Warning was generated by the tag-description rule. s/TrafficSteeringApi.yaml: validated in 100ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 1 warning. ------ Content of the folder ------ BwManagementApi.json BwManagementApi.yaml LICENSE openapi-validation.log README.md TrafficSteeringApi.json TrafficSteeringApi.yaml [Pipeline] updateGitlabCommitStatus [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // gitlabBuilds [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS