search

codeSessionsP2 / masimapage

masima landing page
MIT License
1 stars 2 forks source link

Integrate Travis CI #20

Closed mxklb closed 8 years ago

mxklb commented 8 years ago

We should setup a ci server (travis) to watch our p2coders repository for changes to test them.

It should at least test to build our source code. Later on shall check npm dependencies and could also be used for deployment to the official gh-pages branch. Some static code analysis and maybe tests could be executed as well. I think the way to go is simply using git tags to trigger deployments. With npm and gulp we should not be alone in such a ci build scenario. I think there are already github projects doing exactly this ...

Research is still lacking, I just fire in some link I actually found interesting:

travis-node-project-using-gulp

mxklb commented 8 years ago

travis encrypt -r gh_user/gh_repo "GH_TOKEN=encrypted_token_here" --add defines the env var GH_TOKEN within the .travis.yml file as secure var. This needs to be changed. Due to the git forking workflow we need to set this var individually for each user/fork.

This could easily be achieved by setting the GH_TOKEN var within travis front end directly.

mxklb commented 8 years ago

I activated travis to watch for changes in the master branch and deploy them directly to the gh-pages branch. So actually if we merge in a pull request from our forks, travis shall always build and deploy automatically in background to masima.rocks (including CNAME).

npm dependencies are now also automatically monitored by david ..

Deployment on tags only is TBD. Tests and static code analysis are still missing, also TBD.

mxklb commented 8 years ago

What the title says -> this is done. Travis builds and deploys ..

For the rest new issues shall be created if

are from interest ..