Source code for the meteor application is in a private repository in bitbucket. It is deployed as a dockerised node application in Digital Ocean. Master branch is used for staging and the release branch is used for production. Whenever there is a change in the master branch, velocity tests are to run if it all works, it is to be deployed.
Following link details how it is done using wercker and tutum.
Sample code and the steps explained in a blog
It uses a base velocity test docker image, phantomjs was giving some weird errors initially. All said, it is all working so smoothly. Thought of posting this out as it could be of help to someone with similar scenarios.
Now, to experts in velocity -
As of now, as I understand, there is no ‘unit test’ mode for packages in velocity. If there is a way to do it, can somebody point it out to me. Also, how to get a coverage report and test report persisted using velocity, I don’t find an out of the box solution for it in velocity.Any inputs?