problem with Grunt's placeholder executable #519

Closed
geddski opened this Issue Nov 9, 2012 · 2 comments

Comments

Projects
None yet
3 participants
@geddski
Member

geddski commented Nov 9, 2012

@tkellen I figured out a workaround for the Angular build that was breaking with:
Fatal error: You must install grunt-cli to use the "grunt" command.

I simply added this to the .travis.yml file:

- rm node_modules/.bin/grunt

Now the grunt from grunt-cli is executed instead of the local placeholder.

Glad it's working now. That was a strange occurrence. I had tested it in Mac, Windows, and Linux environments, and the only place it happened was in travis CI for whatever reason. At least we have a recommended workaround now if anyone else sees the same problem. Feel free to mark closed if this workaround is good enough.

@tkellen

This comment has been minimized.

Show comment Hide comment
@tkellen

tkellen Nov 11, 2012

Member

Thanks for posting this Dave. Now that I'm a little more awake, I see that you're running the test suite from your travis config. Can you please try putting your test command in your package.json under scripts like so:

"scripts": {
  "test": "grunt test --in=[Firefox] --reporters=dots"
}

Travis will automatically run npm test after npm install.

It seems the environment for executing scripts defined in .travis.yml must include ./node_modules/.bin in the PATH.

Also, you should be listing your deps in devDependencies, but this shouldn't matter for the issue at hand.

Member

tkellen commented Nov 11, 2012

Thanks for posting this Dave. Now that I'm a little more awake, I see that you're running the test suite from your travis config. Can you please try putting your test command in your package.json under scripts like so:

"scripts": {
  "test": "grunt test --in=[Firefox] --reporters=dots"
}

Travis will automatically run npm test after npm install.

It seems the environment for executing scripts defined in .travis.yml must include ./node_modules/.bin in the PATH.

Also, you should be listing your deps in devDependencies, but this shouldn't matter for the issue at hand.

@tkellen

This comment has been minimized.

Show comment Hide comment
@tkellen

tkellen Nov 11, 2012

Member

Also, could you throw an echo $PATH in your .travis.yml scripts section? I'm just curious to see what it is.

Member

tkellen commented Nov 11, 2012

Also, could you throw an echo $PATH in your .travis.yml scripts section? I'm just curious to see what it is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment