Meteor + CodeShip + module
Anyone can recommend a good script setup to deploy in a module after passing the tests?
I am currently using:
nvm install 0.10.28
nvm use 0.10.28
curl -o meteor_install_script.sh https://install.meteor.com/
chmod +x meteor_install_script.sh
sed -i "s/type sudo >\/dev\/null 2>&1/\ false /g" meteor_install_script.sh
./meteor_install_script.sh
export PATH=$PATH:~/.meteor/
meteor --version
Basically this is what I was able to copy + paste into interwebz and I have no idea what I am doing.
Finally, my test pipeline:
meteor --test
Exiting CodeShip Logs:
I20150515-13:34:16.005(0)? [velocity] mocha is starting a mirror at http://localhost:44995/.
I20150515-13:34:16.006(0)? [velocity] This takes a few minutes the first time.
I20150515-13:34:16.006(0)? [velocity] You can see the mirror logs at: tail -f /home/rof/src/bitbucket.org/atlasshrugs/garden/.meteor/local/log/mocha.log
PASSED mocha : Server initialization => should have a Meteor version defined
Once it hits client side tests, it freezes forever and cannot build.
Any suggestions?
source to share
In accordance with the Velocity readme you should use this command: meteor --test --release velocity:METEOR@1.1.0.3_1
. I was able to get it to work using the following setup commands:
nvm install 0.10.30
nvm use 0.10.30
curl -o meteor_install_script.sh https://install.meteor.com/
chmod +x meteor_install_script.sh
sed -i "s/type sudo >\/dev\/null 2>&1/\ false
/g"meteor_install_script.sh
./meteor_install_script.sh
export PATH=$PATH:~/.meteor/
meteor --version
and this test command (replacing the path to the Meteor app directory. In this case is required sanjo:jasmine
, but if you are using a different tester, you may need to add the appropriate package. The velocity:html-reporter
overkill package for this purpose, but it works, the console reporter should be enough, but I have it not tested):
cd ~/src/bitbucket.org/<path>/ &&
meteor add sanjo:jasmine velocity:html-reporter &&
meteor --test --release velocity:METEOR@1.1.0.3_1
source to share