I wrote this post (https://goo.gl/DR9olx) some time ago, proposing a model to branch and integrate into a CI environment an Android project. Maybe it helps.
2015-09-29 13:14 GMT+02:00 Ray Tayek <[email protected]>: > i, went to this devops meetup > <http://www.meetup.com/Orange-County-DevOps-Meetup/events/225363466/> > tonight. > > speaker did some under the hood stuff using the groovy console and gradle. > > turns out the groovy console repl let's you inspect the current jenkins > instance and fool around with it. > > seem like most of the objects (including the jenkins instance) have a > save() method. this serializes to xml and changes the configuration. > > so you can configure and create jobs dynamically (we don't need no > stinking gui). > > you can also suck in travis-ci/yaml > <http://docs.travis-ci.com/user/customizing-the-build/> files to create > jobs on the fly. > > the speaker's personal GitHub has a somef interesting projects. > https://github.com/samrocketman/ > > For the bootstrapping environment that he used in his talk tonight as well > as that special treat at the end. See the following links: > https://github.com/samrocketman/jenkins-bootstrap-jervis > http://sam.gleske.net/jervis/ <http://sam.gleske.net/jervis/> > > thanks > > > On Tuesday, September 8, 2015 at 1:18:42 PM UTC-7, 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. > -- Enrique López Mañas *Twitter:* http://twitter.com/eenriquelopez *Google+:* http://goo.gl/1PLi2a *Phone:* +34 655 155 199 (ES) +49 157 84281461 (DE) *Site:* http://www.lopez-manas.com -- 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.
