Started by GitLab push by Pietro Piscione Building remotely on Build 3 (selenium docker) in workspace /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-030 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/stf593^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains b0d5b3dfac076822ba7a1694bc987803594d1065 # timeout=10 Checking out Revision b0d5b3dfac076822ba7a1694bc987803594d1065 (origin/stf593) > git config core.sparsecheckout # timeout=10 > git checkout -f b0d5b3dfac076822ba7a1694bc987803594d1065 Commit message: "Added to proto files option java_multiple_files=true; to improve Java code readability." > git rev-list --no-walk 823c898d20512306f1334d9d083c200f69289695 # timeout=10 [mec-gs-030] $ /bin/bash /tmp/jenkins13706502465791167257.sh -- Validating and linting OpenAPI file MEC030_V2XInformationService.yaml... MEC030_V2XInformationService.yaml is valid (node:40221) ExperimentalWarning: The http2 module is an experimental API. Specification is valid, with 0 lint errors --- Validator returned 0, linter returned 0. -- Final validator returns 0. Finished: SUCCESS