Skip to content
This repository has been archived by the owner on Aug 25, 2018. It is now read-only.

Travis integration errors on default settings #49

Closed
fractastical opened this issue Aug 29, 2014 · 7 comments
Closed

Travis integration errors on default settings #49

fractastical opened this issue Aug 29, 2014 · 7 comments
Labels

Comments

@fractastical
Copy link

This error seems to occur on a default install of angular seed:

npm ERR! Error: ENOENT, chmod '/home/travis/build/.../angularfire-seed/node_modules/requirejs/bin/r.js'

screenshot 2014-08-29 12 10 03

Not sure if it is a Travis problem, Angularfire-seed problem or simply a version incompatibility.

Note: adding an ".npmignore" file does not solve this problem.

@katowulf
Copy link
Contributor

Did you check the additional logging in npm-debug.log? I don't think we're going to be much help here as that doesn't look familiar or meaningful. Maybe some node dependency conflicts that could be resolved with sudo npm install or deleting node_modules and trying again?

@fractastical
Copy link
Author

The problem is it's on the travis server, not mine. I don't have access to any of the debug logs, nor running any additional commands.

@jwngr jwngr added the question label Sep 1, 2014
@jwngr
Copy link

jwngr commented Sep 1, 2014

We don't have enough information here to help you out. The ENOENT error is very generic and could mean anything from you not having access to the files to the file paths being incorrect. I've never really seen npm install throw that kind of error. angularfire-seed should work with Travis out of the box. The commands in your prompt do not even look like they are in the latest version of the .travis.yml file, so I'm not sure exactly what code you are running. Maybe you need to upgrade to the latest version of angularfire-seed? Or at least give us more relevant information. Thanks!

@fractastical
Copy link
Author

I can do more troubleshooting, but I pulled a new version of angularfire-seed just before trying to deploy to travs and the only thing I did before deploying was installing dependencies. Do you have any suggestions of commands I can run on local host to see if there is something not correctly working there? From my standpoint everything appears to be working fine locally, it's only when I deploy to travis that I have these weird errors.

@fractastical
Copy link
Author

So i've just run it "out of the box" one more time.

If I import it into travis without running any commands, I get this set of errors:

https://gist.github.com/fractastical/ec73c418f454cbfe3fdc

If I import it after running "npm install" I get this set:

https://gist.github.com/fractastical/08f5c233bf55f9668766

Given that I've tried this a few times without doing anything extra special on my end, I'd be highly surprised if this worked "out of the box" for anyone else.

But maybe I'm missing something...

@jwngr
Copy link

jwngr commented Sep 2, 2014

@katowulf - We should work on getting this repo set up with Travis ourselves to verify that it actually works. Let's get that build badge going for this repo as well. I don't think this will take a lot of work, especially since the .travis.yml file is already written. Then we could back up my claim that it should work out of the box.

@fractastical - Parallel to this discussion, we will look into verifying Travis works with this repo. I'm not sure what you mean by saying that you "imported into Travis without running any commands." Can you share what your .travis.yml file looks like? To be honest, looking at the first error link you provided, the errors look wholly unrelated to angularfire-seed. As for the second, are you actually trying to add angularfire-seed as a dependency in your package.json? That is not going to work since this repo is not published on npm. I still don't think I have enough context here to tell you why things are failing. Shoot me some answers to those questions and we will figure this one out.

@katowulf
Copy link
Contributor

Closed due to inactivity. See #56 for a continuation of Jacob's comments.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants