Commit 8295e742 by Ben Patterson

Fix for spurious 'cb() never called' errors.

Some Jenkins builds are erroring when attempting to set up the
npm environment with the error:

`npm ERR! cb() never called!`

Although it could point to a couple of different things, it is more classically
a sign of a dirty npm environment cache. Cleaning the cache at the start
of any given Jenkins job (which are sourced through this file) should
alleviate the problem.
parent 9d874728
......@@ -24,3 +24,7 @@ source $HOME/edx-venv/bin/activate
# add the node_js packages dir to PATH
PATH=$PATH:node_modules/.bin
# Manage the npm cache on Jenkins.
# (In this case, remove it. That ensures from run-to-run, it is a clean npm environment)
npm cache clean
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment