Disconnect wrote: > Are you doing dream builds or emulator builds? Initially, I would think the focus would be on emulator builds.
> Do you have plans to integrate unapproved fixes? Personally, my goal is 100% automation, meaning if it ain't in a tree somewhere, it ain't getting built. Now, since this is all git-backed, we could evolve where there are sets of builds blending in other sources that are published via their own private git repos. As I noted, though, I'm a n00b on creating build farms, so if nobody else decides to be buildmaster, I want to walk before I run. > That has been a fairly standard problem > with these builds - since most of the google devs don't use the external > tree, it is frequently out of sync or just flat broken. (EG the recent > merge of opencore 2, when the internal cupcake tree is still written to > use opencore 1.) Yup. I expect it will take quite some time for a build farm to generate useful builds, and even after that, there will be lots of times when the farm either can't build (branch head is broken) or generates useless output (e.g., HOME button doesn't work). That's partly an issue of build farm tech and partly an issue of the current Android OSP development process. Over the long haul, we should be able to get this to be as smooth as silk; short-term, it'll be as smooth as a battlefield. But, ya gotta start somewhere. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android App Developer Training: http://commonsware.com/training.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
