Console Output

Started by GitLab push by Hammad Zafar
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-030-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/stf606-draft, 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 2aabbb8d6f54e1d5b6d55c331fda9bd3814c08f9 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 2aabbb8d6f54e1d5b6d55c331fda9bd3814c08f9
Commit message: "Update cli-validate-openapis-mec.sh"
 > git rev-list --no-walk 1b7fd86ec22366ba540a1592a8fd8d054bae57ce # 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-030-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/gs030-vis-api.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:mec/gs030-vis-api.git
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:mec/gs030-vis-api.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse remotes/origin/stf606-draft^{commit} # timeout=10
 > git branch -a -v --no-abbrev --contains 9b8d659216e4a955c92d65486f4225e947873ecb # timeout=10
Checking out Revision 9b8d659216e4a955c92d65486f4225e947873ecb (origin/stf606-draft)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 9b8d659216e4a955c92d65486f4225e947873ecb
Commit message: "update README"
First time build. Skipping changelog.
[Pipeline] }
[Pipeline] // dir
[Pipeline] dir
Running in /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-030-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/stf606-draft, 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 2aabbb8d6f54e1d5b6d55c331fda9bd3814c08f9 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 2aabbb8d6f54e1d5b6d55c331fda9bd3814c08f9
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 ./MEC030_V2XInformationService.yaml: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MEC030_V2XInformationService.yaml... [1] ../specs/MEC030_V2XInformationService.yaml:23:5 at #/tags/2/description Tag object should contain `description` field. 21 | - name: subscription 22 | description: Subscription 23 | - name: QoS | ^^^^^^^^^ 24 | - name: V2X_msg 25 | Warning was generated by the tag-description rule. [2] ../specs/MEC030_V2XInformationService.yaml:24:5 at #/tags/3/description Tag object should contain `description` field. 22 | description: Subscription 23 | - name: QoS 24 | - name: V2X_msg | ^^^^^^^^^^^^^ 25 | 26 | paths: Warning was generated by the tag-description rule. [3] ../specs/MEC030_V2XInformationService.yaml:284:15 at #/paths/~1subscriptions/post/callbacks/notification/{$request.body#~1callbackReference}/post/responses Operation must have at least one `4xx` response. 282 | - $ref: '#/components/schemas/ProvChgPc5Notification' 283 | - $ref: '#/components/schemas/V2xMsgNotification' 284 | responses: | ^^^^^^^^^ 285 | '204': 286 | $ref: '#/components/responses/204' Warning was generated by the operation-4xx-response rule. [4] ../specs/MEC030_V2XInformationService.yaml:1086:5 at #/components/schemas/TestNotification Component: "TestNotification" is never used. 1084 | x-etsi-mec-cardinality: 0..N 1085 | x-etsi-mec-origin-type: Structure (inlined) 1086 | TestNotification: | ^^^^^^^^^^^^^^^^ 1087 | properties: 1088 | _links: Warning was generated by the no-unused-components rule. [5] ../specs/MEC030_V2XInformationService.yaml:1608:5 at #/components/responses/206 Component: "206" is never used. 1606 | '204': 1607 | description: No Content 1608 | '206': | ^^^^^ 1609 | description: Partial content 1610 | '400': Warning was generated by the no-unused-components rule. [6] ../specs/MEC030_V2XInformationService.yaml:1640:5 at #/components/responses/409 Component: "409" is never used. 1638 | schema: 1639 | $ref: '#/components/schemas/ProblemDetails' 1640 | '409': | ^^^^^ 1641 | description: 'Conflict : The operation cannot be executed currently, due to a conflict with the state of the resource' 1642 | content: Warning was generated by the no-unused-components rule. s/MEC030_V2XInformationService.yaml: validated in 208ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 6 warnings.
---- Validating ./MEC030_V2XInformationService.json: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MEC030_V2XInformationService.json... [1] ../specs/MEC030_V2XInformationService.json:32:3 at #/tags/2/description Tag object should contain `description` field. 30 | "description": "Subscription" 31 | }, 32 | { | ^ 33 | "name": "QoS" | ^^^^^^^^^^^^^^^^ 34 | }, | ^^^ 35 | { 36 | "name": "V2X_msg" Warning was generated by the tag-description rule. [2] ../specs/MEC030_V2XInformationService.json:35:3 at #/tags/3/description Tag object should contain `description` field. 33 | "name": "QoS" 34 | }, 35 | { | ^ 36 | "name": "V2X_msg" | ^^^^^^^^^^^^^^^^^^^^ 37 | } | ^^^ 38 | ], 39 | "paths": { Warning was generated by the tag-description rule. [3] ../specs/MEC030_V2XInformationService.json:429:9 at #/paths/~1subscriptions/post/callbacks/notification/{$request.body#~1callbackReference}/post/responses Operation must have at least one `4xx` response. 427 | } 428 | }, 429 | "responses": { | ^^^^^^^^^^^ 430 | "204": { 431 | "$ref": "#/components/responses/204" Warning was generated by the operation-4xx-response rule. [4] ../specs/MEC030_V2XInformationService.json:1358:4 at #/components/schemas/TestNotification Component: "TestNotification" is never used. 1356 | "x-etsi-mec-origin-type": "Structure (inlined)" 1357 | }, 1358 | "TestNotification": { | ^^^^^^^^^^^^^^^^^^ 1359 | "properties": { 1360 | "_links": { Warning was generated by the no-unused-components rule. [5] ../specs/MEC030_V2XInformationService.json:1929:4 at #/components/responses/206 Component: "206" is never used. 1927 | "description": "No Content" 1928 | }, 1929 | "206": { | ^^^^^ 1930 | "description": "Partial content" 1931 | }, Warning was generated by the no-unused-components rule. [6] ../specs/MEC030_V2XInformationService.json:1982:4 at #/components/responses/409 Component: "409" is never used. 1980 | } 1981 | }, 1982 | "409": { | ^^^^^ 1983 | "description": "Conflict : The operation cannot be executed currently, due to a conflict with the state of the resource", 1984 | "content": { Warning was generated by the no-unused-components rule. s/MEC030_V2XInformationService.json: validated in 185ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 6 warnings.


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