Hi Dan,
With the pull request #11, CI will be mostly in place - unit tests, integration tests, acceptance tests, auto build, auto test execution and auto notification.
As a last step, I'm thinking of automating deployment as well. Briefly:
- There will be a branch (possibly master) dedicated to official releases.
- When it is time to make a new release, features and fixes will be merged to the release branch. No activity is allowed besides that.
- After pushing to that branch, post-commit hook will trigger travis-ci service hook and CI make its routine job - get the source code, build, test, verify
- If everything goes well, webapp will be uploaded to the cloud foundry account.