Le 01/04/2016 22:30, Antoine Musso a écrit :
Hello,
The Jenkins slaves had grunt-cli provisioned which is often used by the npm test command. If you get a Jenkins job to fail with:
sh: 1: grunt: not found
Simply add grunt-cli to your project devDependencies and the next build have it installed. Example:
https://gerrit.wikimedia.org/r/#/c/275823/1/package.json,cm
The change removing grunt-cli is: https://gerrit.wikimedia.org/r/#/c/280974/
Hello,
I got rid of grunt-cli local install on all slaves a few minutes ago. So from now on repositories must specific grunt-cli in their devDependencies or CI will complain with: grunt: not found.