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-011-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-011-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/gs011-app-enablement-api.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:mec/gs011-app-enablement-api.git
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:mec/gs011-app-enablement-api.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse remotes/origin/master^{commit} # timeout=10
 > git branch -a -v --no-abbrev --contains 25454d07ae668bd1bde0ea5f8b82190787d9ae21 # timeout=10
Checking out Revision 25454d07ae668bd1bde0ea5f8b82190787d9ae21 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 25454d07ae668bd1bde0ea5f8b82190787d9ae21
Commit message: "Update README.md"
 > git rev-list --no-walk db7413ec65839686dae8e8471eb4d7bfef78590d # timeout=10
[Pipeline] }
[Pipeline] // dir
[Pipeline] dir
Running in /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-011-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 ./MecAppSupportApi.json: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MecAppSupportApi.json... [1] ../specs/MecAppSupportApi.json:20:5 at #/tags/0/description Tag object should contain `description` field. 18 | }, 19 | "tags": [ 20 | { | ^ 21 | "name": "appTrafficRules" | ^^^^^^^^^^^^^^^^^^^^^^^^^ 22 | }, | ^ 23 | { 24 | "name": "appDnsRules" Warning was generated by the tag-description rule. [2] ../specs/MecAppSupportApi.json:23:5 at #/tags/1/description Tag object should contain `description` field. 21 | "name": "appTrafficRules" 22 | }, 23 | { | ^ 24 | "name": "appDnsRules" | ^^^^^^^^^^^^^^^^^^^^^ 25 | }, | ^ 26 | { 27 | "name": "appSubscriptions" Warning was generated by the tag-description rule. [3] ../specs/MecAppSupportApi.json:26:5 at #/tags/2/description Tag object should contain `description` field. 24 | "name": "appDnsRules" 25 | }, 26 | { | ^ 27 | "name": "appSubscriptions" | ^^^^^^^^^^^^^^^^^^^^^^^^^^ 28 | }, | ^ 29 | { 30 | "name": "appConfirmTermination" Warning was generated by the tag-description rule. [4] ../specs/MecAppSupportApi.json:29:5 at #/tags/3/description Tag object should contain `description` field. 27 | "name": "appSubscriptions" 28 | }, 29 | { | ^ 30 | "name": "appConfirmTermination" | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 31 | }, | ^ 32 | { 33 | "name": "appConfirmReady" Warning was generated by the tag-description rule. [5] ../specs/MecAppSupportApi.json:32:5 at #/tags/4/description Tag object should contain `description` field. 30 | "name": "appConfirmTermination" 31 | }, 32 | { | ^ 33 | "name": "appConfirmReady" | ^^^^^^^^^^^^^^^^^^^^^^^^^ 34 | }, | ^ 35 | { 36 | "name": "timing" Warning was generated by the tag-description rule. [6] ../specs/MecAppSupportApi.json:35:5 at #/tags/5/description Tag object should contain `description` field. 33 | "name": "appConfirmReady" 34 | }, 35 | { | ^ 36 | "name": "timing" | ^^^^^^^^^^^^^^^^ 37 | }, | ^ 38 | { 39 | "name": "callbacks" Warning was generated by the tag-description rule. [7] ../specs/MecAppSupportApi.json:38:5 at #/tags/6/description Tag object should contain `description` field. 36 | "name": "timing" 37 | }, 38 | { | ^ 39 | "name": "callbacks" | ^^^^^^^^^^^^^^^^^^^ 40 | } | ^ 41 | ], 42 | "jsonSchemaDialect": "https://json-schema.org/draft/2020-12/schema", Warning was generated by the tag-description rule. [8] ../specs/MecAppSupportApi.json:1107:17 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/AppTerminationNotification/{$request.body#~1callbackUri}/post/responses Operation must have at least one `4xx` response. 1105 | "$ref": "#/components/requestBodies/AppTerminationNotification" 1106 | }, 1107 | "responses": { | ^^^^^^^^^^^ 1108 | "200": { 1109 | "description": "Expected responses from callback consumer, if it accepts the callback" Warning was generated by the operation-4xx-response rule. s/MecAppSupportApi.json: validated in 187ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 8 warnings.
---- Validating ./MecServiceMgmtApi.json: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MecServiceMgmtApi.json... [1] ../specs/MecServiceMgmtApi.json:33:5 at #/tags/0/description Tag object should contain `description` field. 31 | ], 32 | "tags": [ 33 | { | ^ 34 | "name": "appSubscriptions" | ^^^^^^^^^^^^^^^^^^^^^^^^^^ 35 | }, | ^ 36 | { 37 | "name": "appServices" Warning was generated by the tag-description rule. [2] ../specs/MecServiceMgmtApi.json:36:5 at #/tags/1/description Tag object should contain `description` field. 34 | "name": "appSubscriptions" 35 | }, 36 | { | ^ 37 | "name": "appServices" | ^^^^^^^^^^^^^^^^^^^^^ 38 | }, | ^ 39 | { 40 | "name": "services" Warning was generated by the tag-description rule. [3] ../specs/MecServiceMgmtApi.json:39:5 at #/tags/2/description Tag object should contain `description` field. 37 | "name": "appServices" 38 | }, 39 | { | ^ 40 | "name": "services" | ^^^^^^^^^^^^^^^^^^ 41 | }, | ^ 42 | { 43 | "name": "transports" Warning was generated by the tag-description rule. [4] ../specs/MecServiceMgmtApi.json:42:5 at #/tags/3/description Tag object should contain `description` field. 40 | "name": "services" 41 | }, 42 | { | ^ 43 | "name": "transports" | ^^^^^^^^^^^^^^^^^^^^ 44 | }, | ^ 45 | { 46 | "name": "callbacks" Warning was generated by the tag-description rule. [5] ../specs/MecServiceMgmtApi.json:45:5 at #/tags/4/description Tag object should contain `description` field. 43 | "name": "transports" 44 | }, 45 | { | ^ 46 | "name": "callbacks" | ^^^^^^^^^^^^^^^^^^^ 47 | }, | ^ 48 | { 49 | "name": "individualMECservice" Warning was generated by the tag-description rule. [6] ../specs/MecServiceMgmtApi.json:48:5 at #/tags/5/description Tag object should contain `description` field. 46 | "name": "callbacks" 47 | }, 48 | { | ^ 49 | "name": "individualMECservice" | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 50 | } | ^ 51 | ], 52 | "paths": { Warning was generated by the tag-description rule. [7] ../specs/MecServiceMgmtApi.json:259:17 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/ServiceAvailailityNotification/{$request.body#~1callbackReference}/post/responses Operation must have at least one `4xx` response. 257 | "$ref": "#/components/requestBodies/ServiceAvailabilityNotification" 258 | }, 259 | "responses": { | ^^^^^^^^^^^ 260 | "200": { 261 | "description": "Expected responses from callback consumer, if it accepts the callback" Warning was generated by the operation-4xx-response rule. s/MecServiceMgmtApi.json: validated in 189ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 7 warnings.
---- Validating ./MecAppSupportApi.yaml: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MecAppSupportApi.yaml... [1] ../specs/MecAppSupportApi.yaml:15:3 at #/tags/0/description Tag object should contain `description` field. 13 | url: https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/02.02.01_60/gs_MEC011v020201p.pdf 14 | tags: 15 | - name: appTrafficRules | ^^^^^^^^^^^^^^^^^^^^^ 16 | - name: appDnsRules 17 | - name: appSubscriptions Warning was generated by the tag-description rule. [2] ../specs/MecAppSupportApi.yaml:16:3 at #/tags/1/description Tag object should contain `description` field. 14 | tags: 15 | - name: appTrafficRules 16 | - name: appDnsRules | ^^^^^^^^^^^^^^^^^ 17 | - name: appSubscriptions 18 | - name: appConfirmTermination Warning was generated by the tag-description rule. [3] ../specs/MecAppSupportApi.yaml:17:3 at #/tags/2/description Tag object should contain `description` field. 15 | - name: appTrafficRules 16 | - name: appDnsRules 17 | - name: appSubscriptions | ^^^^^^^^^^^^^^^^^^^^^^ 18 | - name: appConfirmTermination 19 | - name: appConfirmReady Warning was generated by the tag-description rule. [4] ../specs/MecAppSupportApi.yaml:18:3 at #/tags/3/description Tag object should contain `description` field. 16 | - name: appDnsRules 17 | - name: appSubscriptions 18 | - name: appConfirmTermination | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ 19 | - name: appConfirmReady 20 | - name: timing Warning was generated by the tag-description rule. [5] ../specs/MecAppSupportApi.yaml:19:3 at #/tags/4/description Tag object should contain `description` field. 17 | - name: appSubscriptions 18 | - name: appConfirmTermination 19 | - name: appConfirmReady | ^^^^^^^^^^^^^^^^^^^^^ 20 | - name: timing 21 | - name: callbacks Warning was generated by the tag-description rule. [6] ../specs/MecAppSupportApi.yaml:20:3 at #/tags/5/description Tag object should contain `description` field. 18 | - name: appConfirmTermination 19 | - name: appConfirmReady 20 | - name: timing | ^^^^^^^^^^^^ 21 | - name: callbacks 22 | jsonSchemaDialect: https://json-schema.org/draft/2020-12/schema Warning was generated by the tag-description rule. [7] ../specs/MecAppSupportApi.yaml:21:3 at #/tags/6/description Tag object should contain `description` field. 19 | - name: appConfirmReady 20 | - name: timing 21 | - name: callbacks | ^^^^^^^^^^^^^^^ 22 | jsonSchemaDialect: https://json-schema.org/draft/2020-12/schema 23 | servers: Warning was generated by the tag-description rule. [8] ../specs/MecAppSupportApi.yaml:704:15 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/AppTerminationNotification/{$request.body#~1callbackUri}/post/responses Operation must have at least one `4xx` response. 702 | requestBody: 703 | $ref: '#/components/requestBodies/AppTerminationNotification' 704 | responses: | ^^^^^^^^^ 705 | '200': 706 | description: Expected responses from callback consumer, if it accepts the callback Warning was generated by the operation-4xx-response rule. s/MecAppSupportApi.yaml: validated in 241ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 8 warnings.
---- Validating ./MecServiceMgmtApi.yaml: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MecServiceMgmtApi.yaml... [1] ../specs/MecServiceMgmtApi.yaml:21:3 at #/tags/0/description Tag object should contain `description` field. 19 | variables: {} 20 | tags: 21 | - name: appSubscriptions | ^^^^^^^^^^^^^^^^^^^^^^ 22 | - name: appServices 23 | - name: services Warning was generated by the tag-description rule. [2] ../specs/MecServiceMgmtApi.yaml:22:3 at #/tags/1/description Tag object should contain `description` field. 20 | tags: 21 | - name: appSubscriptions 22 | - name: appServices | ^^^^^^^^^^^^^^^^^ 23 | - name: services 24 | - name: transports Warning was generated by the tag-description rule. [3] ../specs/MecServiceMgmtApi.yaml:23:3 at #/tags/2/description Tag object should contain `description` field. 21 | - name: appSubscriptions 22 | - name: appServices 23 | - name: services | ^^^^^^^^^^^^^^ 24 | - name: transports 25 | - name: callbacks Warning was generated by the tag-description rule. [4] ../specs/MecServiceMgmtApi.yaml:24:3 at #/tags/3/description Tag object should contain `description` field. 22 | - name: appServices 23 | - name: services 24 | - name: transports | ^^^^^^^^^^^^^^^^ 25 | - name: callbacks 26 | - name: individualMECservice Warning was generated by the tag-description rule. [5] ../specs/MecServiceMgmtApi.yaml:25:3 at #/tags/4/description Tag object should contain `description` field. 23 | - name: services 24 | - name: transports 25 | - name: callbacks | ^^^^^^^^^^^^^^^ 26 | - name: individualMECservice 27 | Warning was generated by the tag-description rule. [6] ../specs/MecServiceMgmtApi.yaml:26:3 at #/tags/5/description Tag object should contain `description` field. 24 | - name: transports 25 | - name: callbacks 26 | - name: individualMECservice | ^^^^^^^^^^^^^^^^^^^^^^^^^^ 27 | 28 | paths: Warning was generated by the tag-description rule. [7] ../specs/MecServiceMgmtApi.yaml:176:15 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/ServiceAvailailityNotification/{$request.body#~1callbackReference}/post/responses Operation must have at least one `4xx` response. 174 | requestBody: 175 | $ref: '#/components/requestBodies/ServiceAvailabilityNotification' 176 | responses: | ^^^^^^^^^ 177 | '200': 178 | description: Expected responses from callback consumer, if it accepts the callback Warning was generated by the operation-4xx-response rule. s/MecServiceMgmtApi.yaml: validated in 235ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 7 warnings.


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