Started by GitLab push by Michele Carignani Building remotely on build.forge.etsi.org (docker) in workspace /home/jenkins/workspace/NFV - Network Functions Virtualisation/sol009 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:nfv/SOL009.git # timeout=10 Fetching upstream changes from git@forge.etsi.org:nfv/SOL009.git > git --version # timeout=10 using GIT_SSH to set credentials > git fetch --tags --progress git@forge.etsi.org:nfv/SOL009.git +refs/heads/*:refs/remotes/origin/* > git rev-parse remotes/origin/validation^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains 89742707edf11b90f684b69ff049fa8a17dda2f2 # timeout=10 Checking out Revision 89742707edf11b90f684b69ff049fa8a17dda2f2 (origin/validation) > git config core.sparsecheckout # timeout=10 > git checkout -f 89742707edf11b90f684b69ff049fa8a17dda2f2 Commit message: "fix permissions" > git rev-list --no-walk c1a5af73864d44c95e5c9061c84548d51b374de6 # timeout=10 [sol009] $ /bin/bash /tmp/jenkins7250007279741844875.sh rm: cannot remove 'build/*-API.yaml': No such file or directory rm: cannot remove 'build/*-API.json': No such file or directory ./build-container.sh: line 7: proxy: command not found http_proxy is not set Proxy set to Sending build context to Docker daemon 13.31kB Step 1/24 : FROM alpine:3.6 3.6: Pulling from library/alpine Digest: sha256:66790a2b79e1ea3e1dabac43990c54aca5d1ddf268d9a5a0285e4167c8b24475 Status: Downloaded newer image for alpine:3.6 ---> 43773d1dba76 Step 2/24 : RUN env ---> Using cache ---> 8f8fd58edd62 Step 3/24 : RUN apk update ---> Using cache ---> b5cdbf75bff8 Step 4/24 : RUN apk add bash ---> Using cache ---> d5b7d5b8474d Step 5/24 : RUN apk add nodejs ---> Using cache ---> 02b0beae235e Step 6/24 : RUN apk add nodejs-npm ---> Using cache ---> c28532e54062 Step 7/24 : RUN apk add asciidoctor ---> Using cache ---> 896cdd5b8441 Step 8/24 : RUN apk add openjdk8 ---> Using cache ---> 33e797dafb78 Step 9/24 : RUN apk add ca-certificates wget && update-ca-certificates ---> Using cache ---> 593f73ca93e7 Step 10/24 : RUN apk add openssl ---> Using cache ---> 9e091baf1530 Step 11/24 : RUN gem install rdoc --pre || gem install rdoc --pre ---> Using cache ---> ac732be97a1c Step 12/24 : RUN gem install asciidoctor-pdf-cjk ---> Using cache ---> c0cc4d048580 Step 13/24 : RUN wget https://forge.etsi.org/swagger2markup-cli-1.3.2.jar ---> Using cache ---> 6fe15e9ad31c Step 14/24 : RUN npm config set proxy $http_proxy ---> Using cache ---> becf94dcbee2 Step 15/24 : RUN npm install -g swagger-tools@0.10.3 ---> Using cache ---> e326d07e34fd Step 16/24 : RUN npm install -g json-refs@3.0.2 ---> Running in 9bf11b794c4d npm WARN invalid config proxy="" npm WARN invalid config Must be a full url with 'http://' npm WARN deprecated superagent@3.8.3: Please note that v5.0.1+ of superagent removes User-Agent header by default, therefore you may need to add it yourself (e.g. GitHub blocks requests without a User-Agent header). This notice will go away with v5.0.2+ once it is released. /usr/bin/json-refs -> /usr/lib/node_modules/json-refs/bin/json-refs /usr/lib `-- json-refs@3.0.2 +-- commander@2.20.3 +-- graphlib@2.1.7 +-- js-yaml@3.13.1 | +-- argparse@1.0.10 | | `-- sprintf-js@1.0.3 | `-- esprima@4.0.1 +-- lodash@4.17.15 +-- native-promise-only@0.8.1 +-- path-loader@1.0.10 | `-- superagent@3.8.3 | +-- component-emitter@1.3.0 | +-- cookiejar@2.1.2 | +-- debug@3.2.6 | | `-- ms@2.1.2 | +-- extend@3.0.2 | +-- form-data@2.5.1 | | +-- asynckit@0.4.0 | | +-- combined-stream@1.0.8 | | | `-- delayed-stream@1.0.0 | | `-- mime-types@2.1.25 | | `-- mime-db@1.42.0 | +-- formidable@1.2.1 | +-- methods@1.1.2 | +-- mime@1.6.0 | +-- qs@6.9.1 | `-- readable-stream@2.3.6 | +-- core-util-is@1.0.2 | +-- inherits@2.0.4 | +-- isarray@1.0.0 | +-- process-nextick-args@2.0.1 | +-- safe-buffer@5.1.2 | +-- string_decoder@1.1.1 | `-- util-deprecate@1.0.2 +-- slash@1.0.0 `-- uri-js@3.0.2 `-- punycode@2.1.1 ---> fc42f7ee9c63 Removing intermediate container 9bf11b794c4d Step 17/24 : RUN npm install -g yamljs@0.3.0 ---> Running in 02fe487d698d npm WARN invalid config proxy="" npm WARN invalid config Must be a full url with 'http://' /usr/bin/yaml2json -> /usr/lib/node_modules/yamljs/bin/yaml2json /usr/bin/json2yaml -> /usr/lib/node_modules/yamljs/bin/json2yaml /usr/lib `-- yamljs@0.3.0 +-- argparse@1.0.10 | `-- sprintf-js@1.0.3 `-- glob@7.1.6 +-- fs.realpath@1.0.0 +-- inflight@1.0.6 | `-- wrappy@1.0.2 +-- inherits@2.0.4 +-- minimatch@3.0.4 | `-- brace-expansion@1.1.11 | +-- balanced-match@1.0.0 | `-- concat-map@0.0.1 +-- once@1.4.0 `-- path-is-absolute@1.0.1 ---> dd78623612c4 Removing intermediate container 02fe487d698d Step 18/24 : ADD validate-in-docker.sh /validate-in-docker.sh ---> 0b9336f849f1 Removing intermediate container 156e71e7e3c4 Step 19/24 : RUN chmod +x /validate-in-docker.sh ---> Running in 20ddb1e8ab0b ---> b6bfbd6eeee3 Removing intermediate container 20ddb1e8ab0b Step 20/24 : ADD swg2mrkup /bin/swg2mrkup ---> 8c2b7781d08e Removing intermediate container 6e91ac7e6931 Step 21/24 : RUN chmod +x /bin/swg2mrkup ---> Running in 86c7bc7e6dba ---> 3f64082c7315 Removing intermediate container 86c7bc7e6dba Step 22/24 : ADD oas2pdf /bin/oas2pdf ---> 848662c6cd83 Removing intermediate container 31bf1fb39dd1 Step 23/24 : RUN chmod +x /bin/oas2pdf ---> Running in 27559c44cbac ---> 3d7780966a46 Removing intermediate container 27559c44cbac Step 24/24 : ENTRYPOINT /validate-in-docker.sh ---> Running in ada75854ff8e ---> 96ab8d0f64c8 Removing intermediate container ada75854ff8e Successfully built 96ab8d0f64c8 Successfully tagged openapivalidator:latest Mounting dir /home/jenkins/workspace/NFV - Network Functions Virtualisation/sol009 as /work mkdir: created directory '/var/www/html/api/nfv/sol009' mkdir: created directory '/var/www/html/api/nfv/sol009/2' Mounting dir /var/www/html/api/nfv/sol009/2 as /storage Using filter '' Entering dir /work/src -- Will validate: ./SOL009/NFVManoLogManagementNotification/NFVManoLogManagementNotification.yaml (api: NFVManoLogManagementNotification) (deliverable:SOL009) --- Merging file. --- Create PDF... --- Validating ../build/SOL009-NFVManoLogManagementNotification-API.yaml mv: can't rename 'SOL009-NFVManoLogManagementNotification-API.pdf': No such file or directory error: Unable to identify the Swagger version for document: ../build/SOL009-NFVManoLogManagementNotification-API.yaml --- Validation done (1). '../build/SOL009-NFVManoLogManagementNotification-API.yaml' -> '/storage/SOL009-NFVManoLogManagementNotification-API.yaml' '../build/SOL009-NFVManoLogManagementNotification-API.json' -> '/storage/SOL009-NFVManoLogManagementNotification-API.json' cp: can't stat '../build/SOL009-NFVManoLogManagementNotification-API.pdf': No such file or directory -- Will validate: ./SOL009/NFVManoLogManagement/NFVManoLogManagement.yaml (api: NFVManoLogManagement) (deliverable:SOL009) --- Merging file. --- Create PDF... mv: can't rename 'SOL009-NFVManoLogManagement-API.pdf': No such file or directory --- Validating ../build/SOL009-NFVManoLogManagement-API.yaml error: Unable to identify the Swagger version for document: ../build/SOL009-NFVManoLogManagement-API.yaml --- Validation done (1). '../build/SOL009-NFVManoLogManagement-API.yaml' -> '/storage/SOL009-NFVManoLogManagement-API.yaml' '../build/SOL009-NFVManoLogManagement-API.json' -> '/storage/SOL009-NFVManoLogManagement-API.json' cp: can't stat '../build/SOL009-NFVManoLogManagement-API.pdf': No such file or directory -- Will validate: ./SOL009/NFVManoConfigurationAndInformationManagement/NFVManoConfigurationAndInformationManagement.yaml (api: NFVManoConfigurationAndInformationManagement) (deliverable:SOL009) --- Merging file. --- Create PDF... mv: can't rename 'SOL009-NFVManoConfigurationAndInformationManagement-API.pdf': No such file or directory --- Validating ../build/SOL009-NFVManoConfigurationAndInformationManagement-API.yaml error: Unable to identify the Swagger version for document: ../build/SOL009-NFVManoConfigurationAndInformationManagement-API.yaml --- Validation done (1). '../build/SOL009-NFVManoConfigurationAndInformationManagement-API.yaml' -> '/storage/SOL009-NFVManoConfigurationAndInformationManagement-API.yaml' '../build/SOL009-NFVManoConfigurationAndInformationManagement-API.json' -> '/storage/SOL009-NFVManoConfigurationAndInformationManagement-API.json' cp: can't stat '../build/SOL009-NFVManoConfigurationAndInformationManagement-API.pdf': No such file or directory -- Will validate: ./SOL009/APIVersion/APIVersion.yaml (api: APIVersion) (deliverable:SOL009) --- Merging file. --- Create PDF... mv: can't rename 'SOL009-APIVersion-API.pdf': No such file or directory --- Validating ../build/SOL009-APIVersion-API.yaml error: Unable to identify the Swagger version for document: ../build/SOL009-APIVersion-API.yaml --- Validation done (1). '../build/SOL009-APIVersion-API.yaml' -> '/storage/SOL009-APIVersion-API.yaml' '../build/SOL009-APIVersion-API.json' -> '/storage/SOL009-APIVersion-API.json' cp: can't stat '../build/SOL009-APIVersion-API.pdf': No such file or directory -- Will validate: ./SOL009/NFVManoPerformanceManagementNotification/NFVManoPerformanceManagementNotification.yaml (api: NFVManoPerformanceManagementNotification) (deliverable:SOL009) --- Merging file. error: Document has invalid references: #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/get/responses/400: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/400 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/get/responses/401: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/401 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/get/responses/403: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/403 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/get/responses/404: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/404 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/get/responses/405: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/405 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/get/responses/406: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/406 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/get/responses/422: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/422 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/get/responses/500: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/500 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/get/responses/503: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/503 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/get/responses/504: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/504 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/post/responses/400: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/400 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/post/responses/401: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/401 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/post/responses/403: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/403 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/post/responses/404: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/404 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/post/responses/405: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/405 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/post/responses/406: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/406 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/post/responses/422: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/422 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/post/responses/500: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/500 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/post/responses/503: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/503 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-PerformanceInformationNotification/post/responses/504: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/504 --- Create PDF... mv: can't rename 'SOL009-NFVManoPerformanceManagementNotification-API.pdf': No such file or directory --- Validating ../build/SOL009-NFVManoPerformanceManagementNotification-API.yaml error: Unsupported Swagger version: undefined --- Validation done (1). '../build/SOL009-NFVManoPerformanceManagementNotification-API.yaml' -> '/storage/SOL009-NFVManoPerformanceManagementNotification-API.yaml' '../build/SOL009-NFVManoPerformanceManagementNotification-API.json' -> '/storage/SOL009-NFVManoPerformanceManagementNotification-API.json' cp: can't stat '../build/SOL009-NFVManoPerformanceManagementNotification-API.pdf': No such file or directory -- Will validate: ./SOL009/NFVManoConfigurationAndInformationManagementNotification/NFVManoConfigurationAndInformationManagementNotification.yaml (api: NFVManoConfigurationAndInformationManagementNotification) (deliverable:SOL009) --- Merging file. error: Document has invalid references: #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/get/responses/400: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/400 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/get/responses/401: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/401 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/get/responses/403: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/403 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/get/responses/404: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/404 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/get/responses/405: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/405 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/get/responses/406: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/406 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/get/responses/422: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/422 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/get/responses/500: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/500 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/get/responses/503: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/503 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/get/responses/504: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/504 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/post/responses/400: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/400 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/post/responses/401: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/401 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/post/responses/403: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/403 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/post/responses/404: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/404 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/post/responses/405: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/405 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/post/responses/406: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/406 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/post/responses/422: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/422 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/post/responses/500: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/500 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/post/responses/503: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/503 #/paths/~1URI-is-provided-by-the-client-when-creating-the-subscription-ConfigurationAndInformationNotification/post/responses/504: JSON Pointer points to missing location: ../responses/SOL009_resp.yaml#/responses/504 --- Create PDF... mv: can't rename 'SOL009-NFVManoConfigurationAndInformationManagementNotification-API.pdf': No such file or directory --- Validating ../build/SOL009-NFVManoConfigurationAndInformationManagementNotification-API.yaml error: Unsupported Swagger version: undefined --- Validation done (1). '../build/SOL009-NFVManoConfigurationAndInformationManagementNotification-API.yaml' -> '/storage/SOL009-NFVManoConfigurationAndInformationManagementNotification-API.yaml' '../build/SOL009-NFVManoConfigurationAndInformationManagementNotification-API.json' -> '/storage/SOL009-NFVManoConfigurationAndInformationManagementNotification-API.json' cp: can't stat '../build/SOL009-NFVManoConfigurationAndInformationManagementNotification-API.pdf': No such file or directory -- Will validate: ./SOL009/NFVManoFaultManagement/NFVManoFaultManagement.yaml (api: NFVManoFaultManagement) (deliverable:SOL009) --- Merging file. --- Create PDF... mv: can't rename 'SOL009-NFVManoFaultManagement-API.pdf': No such file or directory --- Validating ../build/SOL009-NFVManoFaultManagement-API.yaml error: Unable to identify the Swagger version for document: ../build/SOL009-NFVManoFaultManagement-API.yaml --- Validation done (1). '../build/SOL009-NFVManoFaultManagement-API.yaml' -> '/storage/SOL009-NFVManoFaultManagement-API.yaml' '../build/SOL009-NFVManoFaultManagement-API.json' -> '/storage/SOL009-NFVManoFaultManagement-API.json' cp: can't stat '../build/SOL009-NFVManoFaultManagement-API.pdf': No such file or directory -- Will validate: ./SOL009/NFVManoPerformanceManagement/NFVManoPerformanceManagement.yaml (api: NFVManoPerformanceManagement) (deliverable:SOL009) --- Merging file. --- Create PDF... mv: can't rename 'SOL009-NFVManoPerformanceManagement-API.pdf': No such file or directory --- Validating ../build/SOL009-NFVManoPerformanceManagement-API.yaml error: Unable to identify the Swagger version for document: ../build/SOL009-NFVManoPerformanceManagement-API.yaml --- Validation done (1). '../build/SOL009-NFVManoPerformanceManagement-API.yaml' -> '/storage/SOL009-NFVManoPerformanceManagement-API.yaml' '../build/SOL009-NFVManoPerformanceManagement-API.json' -> '/storage/SOL009-NFVManoPerformanceManagement-API.json' cp: can't stat '../build/SOL009-NFVManoPerformanceManagement-API.pdf': No such file or directory -- Will validate: ./SOL009/NFVManoFaultManagementNotification/NFVManoFaultManagementNotification.yaml (api: NFVManoFaultManagementNotification) (deliverable:SOL009) --- Merging file. --- Create PDF... mv: can't rename 'SOL009-NFVManoFaultManagementNotification-API.pdf': No such file or directory --- Validating ../build/SOL009-NFVManoFaultManagementNotification-API.yaml error: Unable to identify the Swagger version for document: ../build/SOL009-NFVManoFaultManagementNotification-API.yaml --- Validation done (1). '../build/SOL009-NFVManoFaultManagementNotification-API.yaml' -> '/storage/SOL009-NFVManoFaultManagementNotification-API.yaml' '../build/SOL009-NFVManoFaultManagementNotification-API.json' -> '/storage/SOL009-NFVManoFaultManagementNotification-API.json' cp: can't stat '../build/SOL009-NFVManoFaultManagementNotification-API.pdf': No such file or directory -- Final validator returns 1. Build step 'Execute shell' marked build as failure Skipped archiving because build is not successful Finished: FAILURE