Started by user DIM Build
Building in workspace /var/jenkins_home/workspace/DIM-Diamant-Angular
using credential jenkins_gitlab
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://gitlab.com/datainmotion/diamant/frontend.git # timeout=10
Fetching upstream changes from https://gitlab.com/datainmotion/diamant/frontend.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials The Gitlab user for the jenkins
> git fetch --tags --progress https://gitlab.com/datainmotion/diamant/frontend.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision b3708dd0703e4c76aeda76159a2bc87e6aff6cad (refs/remotes/origin/develop)
> git config core.sparsecheckout # timeout=10
> git checkout -f b3708dd0703e4c76aeda76159a2bc87e6aff6cad
Commit message: "keycloak theme files"
> git rev-list --no-walk b3708dd0703e4c76aeda76159a2bc87e6aff6cad # timeout=10
$ /var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_12.10/bin/npm install -g @angular/cli bower grunt-cli
npm WARN deprecated bower@1.8.8: We don't recommend using Bower for new projects. Please consider Yarn and Webpack or Parcel. You can read how to migrate legacy project here: https://bower.io/blog/2017/how-to-migrate-away-from-bower/
/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_12.10/bin/ng -> /var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_12.10/lib/node_modules/@angular/cli/bin/ng
/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_12.10/bin/bower -> /var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_12.10/lib/node_modules/bower/bin/bower
/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_12.10/bin/grunt -> /var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_12.10/lib/node_modules/grunt-cli/bin/grunt
> @angular/cli@8.3.3 postinstall /var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_12.10/lib/node_modules/@angular/cli
> node ./bin/postinstall/script.js
+ bower@1.8.8
+ grunt-cli@1.3.2
+ @angular/cli@8.3.3
added 151 packages from 122 contributors and updated 1 package in 10.459s
[DIM-Diamant-Angular] $ /bin/sh -xe /tmp/jenkins5746442416067425864.sh
+ npm run build
> diamant-frontend@0.0.0 build /var/jenkins_home/workspace/DIM-Diamant-Angular
> ng build
An unhandled exception occurred: Could not find module "@angular-devkit/build-angular" from "/var/jenkins_home/workspace/DIM-Diamant-Angular".
See "/tmp/ng-JjJg5M/angular-errors.log" for further details.
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! diamant-frontend@0.0.0 build: `ng build`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the diamant-frontend@0.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! A complete log of this run can be found in:
npm ERR! /var/jenkins_home/.npm/_logs/2019-09-06T13_04_11_949Z-debug.log
Build step 'Execute shell' marked build as failure
Finished: FAILURE