Waiting excitedly for someone to answer this! On Tuesday, September 8, 2015 at 9:18:42 PM UTC+1, Casper Bang wrote: > > I'm looking for a best-practice CI approach for Android apps using > de-facto standard Jenkins, Git and of course Gradle. From what I've seen in > this regard so far (and my own dabbling), Gradle is a step back to Ant > days, as every project ends up with ugly and custom scripting. > > My current setup revolves around a /master branch where new work makes it > into (merged from /feature branches). A push to /master triggers Jenkins > into doing building/verification (debug build), but no actual artefact > distribution (looking into pushing -SNAPSHOT's to a Maven repo). At my > discretion, I merge from /master to /test, which triggers Jenkins into > running Lint and building all flavours of my app, signs etc. (beta build) > and distribute via bash/curl commands (looking into pushing -BETA's to a > standard Maven release repo). Last but not least, I merge from /test to > /release, which makes Jenkins do final builds (looking into publishing to > the Play Store using Google API). > > I'd love to hear your story, what do you consider a good CI "release > train" for Android and do you have public examples to point at? > > Thanks in advance. >
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
