search

JBirdVegas / external_jbirdvegas_mGerrit

mGerrit is a Gerrit instance viewer
19 stars 8 forks source link

Gradle CI build automation #12

Closed JBirdVegas closed 9 years ago

JBirdVegas commented 9 years ago

Attempt to preform automated releases from travis CI builds.

TODO: implement github authorizations

JBirdVegas commented 9 years ago

A note about the travis ci build checks. This commit will change the build to run extra steps if travisBuilder.sh determines the current branch is master.

The extra steps for a master branch are. Build. update version number. commit. push.

Extra steps for release are (version.properties value must end in -release) Build. (verify compilation) Update version number Build (This is the release apk) commit. push, Tag in github

Eventually this will also trigger an upload to the Google Play store in our alpha channel. Then we can promote versions as we see fit.

-1 This probably won't build in master yet

JBirdVegas commented 9 years ago

I started back on this today and discovered I hate it. New plan. I'm going to stand up a jenkins instance for us to release from. This will inject some "doRelease" property which will trigger Google Play uploads. Trying to monitor the branching names, version suffix and env (travis vs local build of master branch) to determine if a release is needed is just too complex to be manageable.