Started by GitLab push by Michele Carignani
Building remotely on build.forge.etsi.org (docker) in workspace /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-016
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/gs016-ue-app-api.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:mec/gs016-ue-app-api.git
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:mec/gs016-ue-app-api.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse remotes/origin/validate-oai3^{commit} # timeout=10
 > git branch -a -v --no-abbrev --contains 576f8176df4ea9db7e34f6de4e87dcc5c43f657c # timeout=10
Checking out Revision 576f8176df4ea9db7e34f6de4e87dcc5c43f657c (origin/validate-oai3)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 576f8176df4ea9db7e34f6de4e87dcc5c43f657c
Commit message: "validation scripts uses swagger-cli and speccy"
First time build. Skipping changelog.
[mec-gs-016] $ /bin/bash /tmp/jenkins8964739052893732767.sh
-- Validatingand linting OpenAPI file UEAppInterfaceApi.json...
UEAppInterfaceApi.json is valid
Specification is valid, with 0 lint errors
--- Validator returned 0, linter returned 0.
-- Validatingand linting OpenAPI file UEAppInterfaceApi.yaml...
UEAppInterfaceApi.yaml is valid
Specification is valid, with 0 lint errors
--- Validator returned 0, linter returned 0.
-- Final validation returns 0.
Finished: SUCCESS