Console Output

Started by an SCM change
Running as SYSTEM
Building in workspace E:\Servers\NodeJS-Dev\L.I. LLC
The recommended git tool is: NONE
No credentials specified
 > git.exe rev-parse --resolve-git-dir E:\Servers\NodeJS-Dev\L.I. LLC\.git # timeout=10
Fetching changes from the remote Git repository
 > git.exe config remote.origin.url /e/Servers/NodeJS-Dev/L.I. LLC.git # timeout=10
Fetching upstream changes from /e/Servers/NodeJS-Dev/L.I. LLC.git
 > git.exe --version # timeout=10
 > git --version # 'git version'
 > git.exe fetch --tags --force --progress -- /e/Servers/NodeJS-Dev/L.I. LLC.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git.exe rev-parse "refs/remotes/origin/master^{commit}" # timeout=10
Checking out Revision 5589384412d3acf346b6bf430b39e3a9ba6c9b67 (refs/remotes/origin/master)
 > git.exe config core.sparsecheckout # timeout=10
 > git.exe checkout -f 5589384412d3acf346b6bf430b39e3a9ba6c9b67 # timeout=10
Commit message: "Merge remote-tracking branch 'origin/master'"
 > git.exe rev-list --no-walk 8770b7dec3ed68feed63aa01cff196519fca593d # timeout=10
[L.I. LLC] $ cmd /c call C:\Windows\TEMP\jenkins3182153556904476744.bat

E:\Servers\NodeJS-Dev\L.I. LLC>npm install 

up to date, audited 271 packages in 2s

17 packages are looking for funding
  run `npm fund` for details

4 high severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
[L.I. LLC] $ cmd /c call C:\Windows\TEMP\jenkins402896225931791745.bat

E:\Servers\NodeJS-Dev\L.I. LLC>test.bat

E:\Servers\NodeJS-Dev\L.I. LLC>pm2 restart app.js 
'pm2' is not recognized as an internal or external command,
operable program or batch file.
Build step 'Execute Windows batch command' marked build as failure
Finished: FAILURE