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 build.forge.etsi.org in /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-014-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-014-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/gs014-ue-identity-api.git # timeout=10 Fetching upstream changes from git@forge.etsi.org:mec/gs014-ue-identity-api.git > git --version # timeout=10 using GIT_SSH to set credentials > git fetch --tags --progress git@forge.etsi.org:mec/gs014-ue-identity-api.git +refs/heads/*:refs/remotes/origin/* > git rev-parse remotes/origin/master^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains af4c47f53991b3a267eb12ee3c3740b32ea6e2c1 # timeout=10 Checking out Revision af4c47f53991b3a267eb12ee3c3740b32ea6e2c1 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f af4c47f53991b3a267eb12ee3c3740b32ea6e2c1 Commit message: "Update README.md" > git rev-list --no-walk 89600a65a38bd44d5aa330aa14cd8e2690ddebf1 # timeout=10 [Pipeline] } [Pipeline] // dir [Pipeline] dir Running in /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-014-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 ./UEidentityAPI.json: No configurations were defined in extends -- using built in recommended configuration by default. validating s/UEidentityAPI.json... [1] ../specs/UEidentityAPI.json:27:11 at #/tags/0/description Tag object should contain `description` field. 25 | "url": "https://127.0.0.1:8081/ui/v1" 26 | }], 27 | "tags": [{ | ^ 28 | "name": "ueIdentityTagInfo" | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 29 | }], | ^^ 30 | "paths": { 31 | "/{appInstanceId}/ue_identity_tag_info": { Warning was generated by the tag-description rule. s/UEidentityAPI.json: validated in 78ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 1 warning. ---- Validating ./UEidentityAPI.yaml: No configurations were defined in extends -- using built in recommended configuration by default. validating s/UEidentityAPI.yaml... [1] ../specs/UEidentityAPI.yaml:20:5 at #/tags/0/description Tag object should contain `description` field. 18 | - url: https://127.0.0.1:8081/ui/v1 19 | tags: 20 | - name: ueIdentityTagInfo | ^^^^^^^^^^^^^^^^^^^^^^^ 21 | paths: 22 | "/{appInstanceId}/ue_identity_tag_info": Warning was generated by the tag-description rule. s/UEidentityAPI.yaml: validated in 80ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 1 warning. ------ Content of the folder ------ LICENSE openapi-validation.log README.md UEidentityAPI.json UEidentityAPI.yaml [Pipeline] updateGitlabCommitStatus [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // gitlabBuilds [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS