Yeoman generator that sets up travis-ci to do automated github pages deployment on every commit.
npm install generator-travis-ci
|1||downloads in the last week|
|32||downloads in the last month|
|Version||0.6.6 last updated 2 months ago|
|Keywords||yeoman-generator, yeoman, generator, travis-ci, travis, github, gh-pages|
|Dependencies (10)||yeoman-generator, q, request, github, open, lodash, ursa, git-tools, travis-ci, chalk|
npm install -g generator-travis-ci
Beta version 1.0 and hopefully all future versions.
Travis is deeply integrated with github, and in order to set all the travis hooks for you, this generator must be run on project hosted on github. Your git remotes should looks something like this:
git remote -v
origin email@example.com:pwmckenna/generator-travis-ci.git (fetch) origin firstname.lastname@example.org:pwmckenna/generator-travis-ci.git (push)
Sets up travis-ci.org to track your project and creates a basic .travis.yml that runs
grunton each commit.
You can then display your projects build/test status in your README or elsewhere like below:
Aims to make yeoman sites work similar to jekyll sites on github pages. Commit the raw files into master and what is served via gh-pages is
grunt buildoutput. For user & organization pages, you specify the branch you'd like to develop in, and the output is pushed to master.
Creates a .travis.yml file that tells travis-ci to build the yeoman project in your master branch after every commit and push the built site into your project's gh-pages branch.
If you have suggestions for common yeoman/grunt testing/deployment tasks that could be handled best by a continuous integration service, make a pull request or shoot me a message!
See the contributing docs