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-013-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-013-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/gs013-location-api.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:mec/gs013-location-api.git
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:mec/gs013-location-api.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse remotes/origin/master^{commit} # timeout=10
 > git branch -a -v --no-abbrev --contains 152787ff1ddc2fba897d56f7936dc97ce69fd736 # timeout=10
Checking out Revision 152787ff1ddc2fba897d56f7936dc97ce69fd736 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 152787ff1ddc2fba897d56f7936dc97ce69fd736
Commit message: "Update README.md"
 > git rev-list --no-walk bf966be78d763ae44254513edbb4224727325a85 # timeout=10
[Pipeline] }
[Pipeline] // dir
[Pipeline] dir
Running in /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-013-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 ./LocationAPI.json: No configurations were defined in extends -- using built in recommended configuration by default. validating s/LocationAPI.json... [1] ../specs/LocationAPI.json:25:5 at #/tags/0/description Tag object should contain `description` field. 23 | ], 24 | "tags": [ 25 | { | ^ 26 | "name": "location" | ^^^^^^^^^^^^^^^^^^ 27 | } | ^ 28 | ], 29 | "paths": { Warning was generated by the tag-description rule. [2] ../specs/LocationAPI.json:346:9 at #/paths/~1subscriptions~1area~1circle/get/responses Operation must have at least one `4xx` response. 344 | "description": "This operation is used for retrieving all active subscriptions to area change notifications.", 345 | "operationId": "areaCircleSubListGET", 346 | "responses": { | ^^^^^^^^^^^ 347 | "200": { 348 | "description": "Response to retrieve area subscriptions", Warning was generated by the operation-4xx-response rule. [3] ../specs/LocationAPI.json:534:17 at #/paths/~1subscriptions~1area~1circle/post/callbacks/notification/{$request.body#~1circleNotificationSubscription.callbackReference.notifyURL}/post/responses Operation must have at least one `4xx` response. 532 | } 533 | }, 534 | "responses": { | ^^^^^^^^^^^ 535 | "204": { 536 | "$ref": "#/components/responses/204" Warning was generated by the operation-4xx-response rule. [4] ../specs/LocationAPI.json:760:9 at #/paths/~1subscriptions~1distance/get/responses Operation must have at least one `4xx` response. 758 | "description": "This operation is used for retrieving all active subscriptions to a distance change notifications.", 759 | "operationId": "distanceSubListGET", 760 | "responses": { | ^^^^^^^^^^^ 761 | "200": { 762 | "description": "Response to retrieve area subscriptions", Warning was generated by the operation-4xx-response rule. [5] ../specs/LocationAPI.json:964:17 at #/paths/~1subscriptions~1distance/post/callbacks/notification/{$request.body#~1distanceNotificationSubscription.callbackReference.notifyURL}/post/responses Operation must have at least one `4xx` response. 962 | } 963 | }, 964 | "responses": { | ^^^^^^^^^^^ 965 | "204": { 966 | "$ref": "#/components/responses/204" Warning was generated by the operation-4xx-response rule. [6] ../specs/LocationAPI.json:1187:9 at #/paths/~1subscriptions~1periodic/get/responses Operation must have at least one `4xx` response. 1185 | "description": "This operation is used for retrieving all active subscriptions to periodic notifications.", 1186 | "operationId": "periodicSubListGET", 1187 | "responses": { | ^^^^^^^^^^^ 1188 | "200": { 1189 | "description": "Response to retrieve area subscriptions", Warning was generated by the operation-4xx-response rule. [7] ../specs/LocationAPI.json:1359:17 at #/paths/~1subscriptions~1periodic/post/callbacks/notification/{$request.body#~1periodicNotificationSubscription.callbackReference.notifyURL}/post/responses Operation must have at least one `4xx` response. 1357 | } 1358 | }, 1359 | "responses": { | ^^^^^^^^^^^ 1360 | "204": { 1361 | "$ref": "#/components/responses/204" Warning was generated by the operation-4xx-response rule. [8] ../specs/LocationAPI.json:1570:9 at #/paths/~1subscriptions~1userTracking/get/responses Operation must have at least one `4xx` response. 1568 | "description": "This operation is used for retrieving all active subscriptions to user tracking notifications.", 1569 | "operationId": "userTrackingSubListGET", 1570 | "responses": { | ^^^^^^^^^^^ 1571 | "200": { 1572 | "description": "Response to retrieve user tracking subscriptions", Warning was generated by the operation-4xx-response rule. [9] ../specs/LocationAPI.json:1740:17 at #/paths/~1subscriptions~1userTracking/post/callbacks/notification/{$request.body#~1userTrackingSubscription.callbackReference.notifyURL}/post/responses Operation must have at least one `4xx` response. 1738 | } 1739 | }, 1740 | "responses": { | ^^^^^^^^^^^ 1741 | "204": { 1742 | "$ref": "#/components/responses/204" Warning was generated by the operation-4xx-response rule. [10] ../specs/LocationAPI.json:1945:9 at #/paths/~1subscriptions~1zonalTraffic/get/responses Operation must have at least one `4xx` response. 1943 | "description": "This operation is used for retrieving all active subscriptions to zonal traffic change notifications.", 1944 | "operationId": "zonalTrafficSubListGET", 1945 | "responses": { | ^^^^^^^^^^^ 1946 | "200": { 1947 | "description": "Response to retrieve zonal traffic subscriptions", Warning was generated by the operation-4xx-response rule. [11] ../specs/LocationAPI.json:2115:17 at #/paths/~1subscriptions~1zonalTraffic/post/callbacks/notification/{$request.body#~1zonalTrafficSubscription.callbackReference.notifyURL}/post/responses Operation must have at least one `4xx` response. 2113 | } 2114 | }, 2115 | "responses": { | ^^^^^^^^^^^ 2116 | "204": { 2117 | "$ref": "#/components/responses/204" Warning was generated by the operation-4xx-response rule. [12] ../specs/LocationAPI.json:2320:9 at #/paths/~1subscriptions~1zoneStatus/get/responses Operation must have at least one `4xx` response. 2318 | "description": "This operation is used for retrieving all active subscriptions to zone status change notifications.", 2319 | "operationId": "zoneStatusSubListGET", 2320 | "responses": { | ^^^^^^^^^^^ 2321 | "200": { 2322 | "description": "Response to retrieve zone status subscriptions", Warning was generated by the operation-4xx-response rule. [13] ../specs/LocationAPI.json:2484:17 at #/paths/~1subscriptions~1zoneStatus/post/callbacks/notification/{$request.body#~1zoneStatusSubscription.callbackReference.notifyURL}/post/responses Operation must have at least one `4xx` response. 2482 | } 2483 | }, 2484 | "responses": { | ^^^^^^^^^^^ 2485 | "204": { 2486 | "$ref": "#/components/responses/204" Warning was generated by the operation-4xx-response rule. [14] ../specs/LocationAPI.json:2689:7 at #/components/responses/200 Component: "200" is never used. 2687 | "components": { 2688 | "responses": { 2689 | "200": { | ^^^^^ 2690 | "description": "OK" 2691 | }, Warning was generated by the no-unused-components rule. [15] ../specs/LocationAPI.json:2755:7 at #/components/responses/414 Component: "414" is never used. 2753 | } 2754 | }, 2755 | "414": { | ^^^^^ 2756 | "description": "URI Too Long : used to indicate that the server is refusing to process the request because the request URI is longer th...<33 chars> 2757 | "content": { Warning was generated by the no-unused-components rule. [16] ../specs/LocationAPI.json:2765:7 at #/components/responses/415 Component: "415" is never used. 2763 | } 2764 | }, 2765 | "415": { | ^^^^^ 2766 | "description": "Unsupported Media Type : used to indicate that the server or the client does not support the content type of the entity body.", 2767 | "content": { Warning was generated by the no-unused-components rule. s/LocationAPI.json: validated in 268ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 16 warnings.
---- Validating ./LocationAPI.yaml: No configurations were defined in extends -- using built in recommended configuration by default. validating s/LocationAPI.yaml... [1] ../specs/LocationAPI.yaml:17:5 at #/tags/0/description Tag object should contain `description` field. 15 | - url: 'https://localhost/location/v2' 16 | tags: 17 | - name: 'location' | ^^^^^^^^^^^^^^^^ 18 | paths: 19 | /queries/distance: Warning was generated by the tag-description rule. [2] ../specs/LocationAPI.yaml:223:7 at #/paths/~1subscriptions~1area~1circle/get/responses Operation must have at least one `4xx` response. 221 | description: 'This operation is used for retrieving all active subscriptions to area change notifications.' 222 | operationId: areaCircleSubListGET 223 | responses: | ^^^^^^^^^ 224 | '200': 225 | description: 'Response to retrieve area subscriptions' Warning was generated by the operation-4xx-response rule. [3] ../specs/LocationAPI.yaml:354:15 at #/paths/~1subscriptions~1area~1circle/post/callbacks/notification/{$request.body#~1circleNotificationSubscription.callbackReference.notifyURL}/post/responses Operation must have at least one `4xx` response. 352 | nanoSeconds": 0 353 | locationRetrievalStatus: 'Retrieved' 354 | responses: | ^^^^^^^^^ 355 | '204': 356 | $ref: '#/components/responses/204' Warning was generated by the operation-4xx-response rule. [4] ../specs/LocationAPI.yaml:509:7 at #/paths/~1subscriptions~1distance/get/responses Operation must have at least one `4xx` response. 507 | description: 'This operation is used for retrieving all active subscriptions to a distance change notifications.' 508 | operationId: distanceSubListGET 509 | responses: | ^^^^^^^^^ 510 | '200': 511 | description: 'Response to retrieve area subscriptions' Warning was generated by the operation-4xx-response rule. [5] ../specs/LocationAPI.yaml:653:15 at #/paths/~1subscriptions~1distance/post/callbacks/notification/{$request.body#~1distanceNotificationSubscription.callbackReference.notifyURL}/post/responses Operation must have at least one `4xx` response. 651 | nanoSeconds": 0 652 | locationRetrievalStatus: 'Retrieved' 653 | responses: | ^^^^^^^^^ 654 | '204': 655 | $ref: '#/components/responses/204' Warning was generated by the operation-4xx-response rule. [6] ../specs/LocationAPI.yaml:811:7 at #/paths/~1subscriptions~1periodic/get/responses Operation must have at least one `4xx` response. 809 | description: 'This operation is used for retrieving all active subscriptions to periodic notifications.' 810 | operationId: periodicSubListGET 811 | responses: | ^^^^^^^^^ 812 | '200': 813 | description: 'Response to retrieve area subscriptions' Warning was generated by the operation-4xx-response rule. [7] ../specs/LocationAPI.yaml:926:15 at #/paths/~1subscriptions~1periodic/post/callbacks/notification/{$request.body#~1periodicNotificationSubscription.callbackReference.notifyURL}/post/responses Operation must have at least one `4xx` response. 924 | nanoSeconds": 0 925 | locationRetrievalStatus: 'Retrieved' 926 | responses: | ^^^^^^^^^ 927 | '204': 928 | $ref: '#/components/responses/204' Warning was generated by the operation-4xx-response rule. [8] ../specs/LocationAPI.yaml:1066:7 at #/paths/~1subscriptions~1userTracking/get/responses Operation must have at least one `4xx` response. 1064 | description: 'This operation is used for retrieving all active subscriptions to user tracking notifications.' 1065 | operationId: userTrackingSubListGET 1066 | responses: | ^^^^^^^^^ 1067 | '200': 1068 | description: 'Response to retrieve user tracking subscriptions' Warning was generated by the operation-4xx-response rule. [9] ../specs/LocationAPI.yaml:1178:15 at #/paths/~1subscriptions~1userTracking/post/callbacks/notification/{$request.body#~1userTrackingSubscription.callbackReference.notifyURL}/post/responses Operation must have at least one `4xx` response. 1176 | rel: UserTrackingSubscription 1177 | href: 'http://meAppServer.example.com/location/v2/subscriptions/userTracking/sub123' 1178 | responses: | ^^^^^^^^^ 1179 | '204': 1180 | $ref: '#/components/responses/204' Warning was generated by the operation-4xx-response rule. [10] ../specs/LocationAPI.yaml:1312:7 at #/paths/~1subscriptions~1zonalTraffic/get/responses Operation must have at least one `4xx` response. 1310 | description: 'This operation is used for retrieving all active subscriptions to zonal traffic change notifications.' 1311 | operationId: zonalTrafficSubListGET 1312 | responses: | ^^^^^^^^^ 1313 | '200': 1314 | description: 'Response to retrieve zonal traffic subscriptions' Warning was generated by the operation-4xx-response rule. [11] ../specs/LocationAPI.yaml:1424:15 at #/paths/~1subscriptions~1zonalTraffic/post/callbacks/notification/{$request.body#~1zonalTrafficSubscription.callbackReference.notifyURL}/post/responses Operation must have at least one `4xx` response. 1422 | rel: ZonalTrafficSubscription 1423 | href: 'http://meAppServer.example.com/location/v2/subscriptions/zonalTraffic/sub123' 1424 | responses: | ^^^^^^^^^ 1425 | '204': 1426 | $ref: '#/components/responses/204' Warning was generated by the operation-4xx-response rule. [12] ../specs/LocationAPI.yaml:1558:7 at #/paths/~1subscriptions~1zoneStatus/get/responses Operation must have at least one `4xx` response. 1556 | description: 'This operation is used for retrieving all active subscriptions to zone status change notifications.' 1557 | operationId: zoneStatusSubListGET 1558 | responses: | ^^^^^^^^^ 1559 | '200': 1560 | description: 'Response to retrieve zone status subscriptions' Warning was generated by the operation-4xx-response rule. [13] ../specs/LocationAPI.yaml:1667:15 at #/paths/~1subscriptions~1zoneStatus/post/callbacks/notification/{$request.body#~1zoneStatusSubscription.callbackReference.notifyURL}/post/responses Operation must have at least one `4xx` response. 1665 | rel: ZoneStatusSubscription 1666 | href: 'http://meAppServer.example.com/location/v2/subscriptions/zoneStatus/sub123' 1667 | responses: | ^^^^^^^^^ 1668 | '204': 1669 | $ref: '#/components/responses/204' Warning was generated by the operation-4xx-response rule. [14] ../specs/LocationAPI.yaml:1799:5 at #/components/responses/200 Component: "200" is never used. 1797 | components: 1798 | responses: 1799 | '200': | ^^^^^ 1800 | description: 'OK' 1801 | '204': Warning was generated by the no-unused-components rule. [15] ../specs/LocationAPI.yaml:1841:5 at #/components/responses/414 Component: "414" is never used. 1839 | schema: 1840 | $ref: '#/components/schemas/ProblemDetails' 1841 | '414': | ^^^^^ 1842 | description: 1843 | 'URI Too Long : used to indicate that the server is refusing to process the request because the request URI is Warning was generated by the no-unused-components rule. [16] ../specs/LocationAPI.yaml:1849:5 at #/components/responses/415 Component: "415" is never used. 1847 | schema: 1848 | $ref: '#/components/schemas/ProblemDetails' 1849 | '415': | ^^^^^ 1850 | description: 'Unsupported Media Type : used to indicate that the server or the client does not support the content type of the entity body.' 1851 | content: Warning was generated by the no-unused-components rule. s/LocationAPI.yaml: validated in 297ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 16 warnings.


------ Content of the folder ------
LICENSE
LocationAPI.json
LocationAPI.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