-
Notifications
You must be signed in to change notification settings - Fork 744
v0.6.0 - shell.cp('r', '/foo/*, '/bar') fails with /foo/* no such file or directory #342
Copy link
Copy link
Closed
Description
Hi,
I am using shelljs for a long time now. My Jenkins always pulls the latest version and until v0.5.3 everything works nice. But with 0.6.0 something broke.
When I do:
var font = {
font: 'fontawesome',
fontSourceDir: './node_modules/font-awesome/fonts/*',
fontTargetDir: '/stuff/build/prod/fonts/'
};
console.log(' build font: ' + font.fontSourceDir + ' > ' + font.fontTargetDir);
console.log(' current-Dir: ' + shell.pwd());
shell.mkdir('-p', font.fontTargetDir);
shell.cp('-R', font.fontSourceDir, font.fontTargetDir);
I get the error
build font: ./node_modules/font-awesome/fonts/* > ./stuff/build/prod/fonts/
current-Dir: /opt/jenkins/jobs/example.com_website--dev-preview/workspace
shell.js: internal error
Error: ENOENT, no such file or directory './node_modules/font-awesome/fonts/*'
at Object.fs.statSync (fs.js:689:18)
at /opt/jenkins/jobs/example.com_website--dev-preview/workspace/node_modules/shelljs/src/cp.js:148:21
at Array.forEach (native)
at Object._cp (/opt/jenkins/jobs/example.com_website--dev-preview/workspace/node_modules/shelljs/src/cp.js:144:13)
at Object.cp (/opt/jenkins/jobs/example.com_website--dev-preview/workspace/node_modules/shelljs/src/common.js:240:23)
at /opt/jenkins/jobs/example.com_website--dev-preview/workspace/stuff/build-scripts/build-tasks-def.js:312:15
at /opt/jenkins/jobs/example.com_website--dev-preview/workspace/node_modules/async/lib/async.js:181:20
at Object.async.forEachOf.async.eachOf (/opt/jenkins/jobs/example.com_website--dev-preview/workspace/node_modules/async/lib/async.js:233:13)
at Object.async.forEach.async.each (/opt/jenkins/jobs/example.com_website--dev-preview/workspace/node_modules/async/lib/async.js:209:22)
at Object.exports.buildFonts (/opt/jenkins/jobs/example.com_website--dev-preview/workspace/stuff/build-scripts/build-tasks-def.js:308:11)
npm ERR! weird error 1
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
npm ERR! not ok code 0
Using ubuntu with apt-get install nodejs-legacy in version
# npm -version
1.3.10
# node -v
v0.10.25
Do I have the wrong node version or is this really a bug?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels