nvdnkpr / tinci

TINy Continuous Integration script for use with GIT hooks

tinci

TINy Continuous Integration script for use with Git hooks

For the looks

You can setup tinci for a bare Git repo and view the build logs over HTTP.

$ npm install -g tinci
$ tinci my/project.git/
$ open http://localhost:4567

Invoke a fetch and build with WebHooks by doing a HTTP POST to http://localhost:4567?invoke. More on WebHooks and integration with GitHub.

Just the hooks

If you don't want the GUI then you can just copy the hook script to your Git repo manualy.

$ cp tinci/hooks/post-receive project.git/hooks/
$ git config -f project.git/config --add tinci.runner "make test"

tinci will now run the shell command 'make test' each time someone pushes to your repos master branch.

To run tinci on another branch or tag.

$ git config -f project.git/config --add tinci.match my-feature

The tinci.match setting uses regexp so you can specify tinci to run on all pushes by giving the value .*.

tinci will execute its own hooks on completion of a job. Place executable files in your repos hooks directory with the name tinci, tinci-<branch>, tinci-success or tinci-fail.

Each hook script will be called with the following arguments:

1. path to work directory
2. current job's exit code
3. last job's exit code

The tinci and tinci-<branch> hooks will be called on all completed jobs. tinci-success is only called on a job that exits with a zero and tinci-fail will only be called when a job exits with non-zero.

<branch> in tinci-<branch> will be replaced with the current short ref name of the current job.

Example: git push origin master:deploy till trigger a tinci job on the deploy branch on origin and will look for and execute a hook script with the name tinci-deploy.

These hooks are compatible with post-receive, in other words each script will be called with the same stdin value as the post-receive was.

Here is a sample fail hook for sending e-mail and a hook which syncs files on deploy branch to Amazon S3.