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-029
[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-029/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/gs029-fai-api.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:mec/gs029-fai-api.git
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:mec/gs029-fai-api.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse remotes/origin/stf606-draft^{commit} # timeout=10
 > git branch -a -v --no-abbrev --contains 75e893c8c61e21a3c621da7650dce351d6a0a832 # timeout=10
Checking out Revision 75e893c8c61e21a3c621da7650dce351d6a0a832 (origin/stf606-draft)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 75e893c8c61e21a3c621da7650dce351d6a0a832
Commit message: "update README"
 > git rev-list --no-walk 2e50359f3605e5e3b4a111459d39b4c878e05c0a # timeout=10
[Pipeline] }
[Pipeline] // dir
[Pipeline] dir
Running in /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-029/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 ./MEC029_FAI.yaml: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MEC029_FAI.yaml... [1] ../specs/MEC029_FAI.yaml:1304:5 at #/components/schemas/ExpiryNotification Component: "ExpiryNotification" is never used. 1302 | type: object 1303 | x-etsi-mec-cardinality: "1" 1304 | ExpiryNotification: | ^^^^^^^^^^^^^^^^^^ 1305 | properties: 1306 | _links: Warning was generated by the no-unused-components rule. [2] ../specs/MEC029_FAI.yaml:1780:5 at #/components/schemas/TestNotification Component: "TestNotification" is never used. 1778 | x-etsi-ref: 6.3.5 1779 | 1780 | TestNotification: | ^^^^^^^^^^^^^^^^ 1781 | type: object 1782 | required: Warning was generated by the no-unused-components rule. [3] ../specs/MEC029_FAI.yaml:1999:5 at #/components/responses/206 Component: "206" is never used. 1997 | "204": 1998 | description: No Content 1999 | "206": | ^^^^^ 2000 | description: Partial content 2001 | "400": Warning was generated by the no-unused-components rule. [4] ../specs/MEC029_FAI.yaml:2031:5 at #/components/responses/409 Component: "409" is never used. 2029 | schema: 2030 | $ref: "#/components/schemas/ProblemDetails" 2031 | "409": | ^^^^^ 2032 | description: "Conflict : The operation cannot be executed currently, due to a conflict with the state of the resource" 2033 | content: Warning was generated by the no-unused-components rule. s/MEC029_FAI.yaml: validated in 245ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 4 warnings.
---- Validating ./MEC029_FAI.json: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MEC029_FAI.json... [1] ../specs/MEC029_FAI.json:1677:7 at #/components/schemas/ExpiryNotification Component: "ExpiryNotification" is never used. 1675 | "x-etsi-mec-cardinality": "1" 1676 | }, 1677 | "ExpiryNotification": { | ^^^^^^^^^^^^^^^^^^^^ 1678 | "properties": { 1679 | "_links": { Warning was generated by the no-unused-components rule. [2] ../specs/MEC029_FAI.json:2217:7 at #/components/schemas/TestNotification Component: "TestNotification" is never used. 2215 | "x-etsi-ref": "6.3.5" 2216 | }, 2217 | "TestNotification": { | ^^^^^^^^^^^^^^^^^^ 2218 | "type": "object", 2219 | "required": [ Warning was generated by the no-unused-components rule. [3] ../specs/MEC029_FAI.json:2455:7 at #/components/responses/206 Component: "206" is never used. 2453 | "description": "No Content" 2454 | }, 2455 | "206": { | ^^^^^ 2456 | "description": "Partial content" 2457 | }, Warning was generated by the no-unused-components rule. [4] ../specs/MEC029_FAI.json:2508:7 at #/components/responses/409 Component: "409" is never used. 2506 | } 2507 | }, 2508 | "409": { | ^^^^^ 2509 | "description": "Conflict : The operation cannot be executed currently, due to a conflict with the state of the resource", 2510 | "content": { Warning was generated by the no-unused-components rule. s/MEC029_FAI.json: validated in 216ms Woohoo! Your OpenAPI definition is valid. 🎉 You have 4 warnings.


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