Integarte CI into a play-cms
This merge request introduces CI integration for the play-cms. CI configuration contains following jobs:
- check-headers - ensure that license headers were set. It is triggered for the tags and merge requiests
- test - run play-cms test suite. executed always
- publish - publishes new play-cms version to the bintray. executed only for tags.
- build-demo - ties play-cms with the demo project, to ensure that demo wasn't broken after play-cms changed. executed only for master branch and stable version branches (e.g. 2.5.x).
Demo project already updated to fit this CI - 2.5.x branch was created and updated to depend on the last stable release of the play-cms. Master depends on the unreleased play-cms version (2.6.0), however this is ok since it should be run against play-cms master.
Changes that should be done in the release process:
- releases should be triggered by pushing new tags into a repository
- with each new major release new branch should be created as well
- Branch with the same name should be also created in the demo repository
- In demo master branch play-cms version should be bumped to the next upcoming version