Allow Travis build system to perform a deploy/release when requested.
- Dominant language
- Java
- Stars
- 287
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
Pull Request #307 was added to provide a systematic way to "request" a release of SageTV.
TravisCI will read the last git commit message and if that message contains `[ci release]` then this script will push to Bintray as a release, tagging the release with the `VERSION` tag.
eg, if the message was `"Updated release version [ci release]"` then this script will push the release to Bintray `AFTER` a successful build that is `NOT` a pull request.
It will then `git tag` the release with the `VERSION` tag and then `push` that tag to github.
The goal here is to have the releasing to Bintray something that happens automatically based on the commit message, so that we can remove myself from the "build/release" blocking loop.
The flow for this might be something like this...
Someone updates the Version.java and CHANGELOG.md files with the release information, and then commits that using the `[ci release]` message. Travis will do a full build, and then release it.
I'm leaving this open, until we work out all the kinks in the system. Last night I did use `[ci release]` and it did push a release to bintry but the tagging did not work. I made some changes to the tagging, so we'll see for the next release if the tagging happens or not.
Contributor guide
Assessment
This issue has not been assessed yet.