-
Notifications
You must be signed in to change notification settings - Fork 360
Conversation
Problem coming from Would you mind updating our phantomjs package? |
@mmahalwy That's not Also, updated how travis pickup the right node version since it was using node |
add `.nvrmc` for two reasons: - travis uses `nvm` by default to manage node versions. - It will make it easy for contributers who use `nvm` to use the proper node version locally too.
f2e5007
to
5675c6f
Compare
jenkins does use 6.3 (it uses the same configuration as the complaint from Jenkins is:
jenkins build using prod. |
Thanks for posting this because I can't see the errors myself, will have a look at this tomorrow. |
@@ -1,8 +1,6 @@ | |||
sudo: false | |||
language: node_js | |||
env: TEST_SUITE=unit | |||
node_js: | |||
- "5.6.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i prefer putting 6.3.0 here instead of .nvmrc
just because it will save a lot of pain in the future (next time Travis breaks, people will immediately open .travis.yml
, and it may not be obvious to someone else that they need to look at .nvmrc
).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can add a comment too saying that the node version is handled in .nvmrc
.
Also most of the time travis breaks it will be something else plus travis already shows the version in the log & also that it picks it up from nvm
.
I'm planning to make the tools & build process more robust so that things doesn't break unless it's something major.
Deployed to: http://staging.quran.com:32839 |
Deployed to: http://staging.quran.com:32840 |
Deployed to: http://staging.quran.com:32841 |
Looks good to me. let me know if this is ready to be merged. |
@@ -18,7 +18,7 @@ RUN cp /etc/cron.daily/logrotate /etc/cron.hourly | |||
# cache npm install when package.json hasn't changed | |||
WORKDIR /tmp | |||
ADD package.json package.json | |||
RUN npm install | |||
RUN npm install --silent --no-progress |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
technically, we should eventually add --production
to it. So we aren't downloading unneeded dependencies like phantomjs or karma
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True, but then travis will fail because the karma test that runs on travis requires phantomjs
Deployed to: http://staging.quran.com:32845 |
@sabeurthabti It's ok form my side too, but to be sure I will just do one last check today afternoon. |
Deployed to: http://staging.quran.com:32846 |
@sabeurthabti You can merge this now. I'll follow up with a new PR to do more cleanup, but for now this is good to go 👍 |
lgtm |
Thank you @ahmedelgabri |
Thanks @ahmedelgabri ! |
package.json
npm
scripts adds executables form thenode_modules
folder in$PATH
automatically so you can just reference the executable only without the path.stylelintrc
indentationwebpack/
folder