Want to help with Android nightly builds?

by Mark Murphy » Sat, 11 Apr 2009 08:01:58 GMT


Sponsored Links
 A few folk are starting to build the infrastructure for a nightly build
farm, to extend Al Sutton's groundbreaking work on creating downloadable
SDKs out of the public Android repositories.

It will take some time for us to get everything together, including
working out the kinks in the Android development process itself -- see
David Turner's post on this thread:




Want to help with Android nightly builds?

by Disconnect » Sun, 12 Apr 2009 00:21:24 GMT


 re you doing dream builds or emulator builds?

FYI I haven't discontinued my dream builds - I've been focusing on the work
some people have done to get actual, working google services into master.
(And it seems like despite the opening of donut and the claimed 'real soon
now' release of cupcake, they have recently merged in a bunch of changes
that break basically everything. Audio, make/break calls, etc are all broken
in the newest trees.)

Do you have plans to integrate unapproved fixes? (Either fixes in the review
system that aren't pushed to the tree yet, or fixes that didn't make it
there to begin with.) 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.) And
if you are trying to do dream builds, its even worse - updated hw support
binaries, etc.

(For those few remaining people who don't know :) my g1 cupcake/master
builds are at http://andblogs.net/images/snapshots. 3/16 is reportedly quite
stable.)

On Fri, Apr 10, 2009 at 8:01 PM, Mark Murphy <mmur...@commonsware.com>wrote:


--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Want to help with Android nightly builds?

by Mark Murphy » Sun, 12 Apr 2009 01:10:15 GMT


 


Initially, I would think the focus would be on emulator builds.


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.


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 

--~--~---------~--~----~------------~-------~--~----~



Want to help with Android nightly builds?

by Incognito » Sun, 12 Apr 2009 21:08:38 GMT


 The whole technical aspect sounds interesting. What are the actual programs 
that people have to run to accomplish the nightly builds? You have any links 
anywhere?





A few folk are starting to build the infrastructure for a nightly build
farm, to extend Al Sutton's groundbreaking work on creating downloadable
SDKs out of the public Android repositories.

It will take some time for us to get everything together, including
working out the kinks in the Android development process itself -- see
David Turner's post on this thread:




Want to help with Android nightly builds?

by Mark Murphy » Sun, 12 Apr 2009 23:07:13 GMT


 


I believe the build slaves are not running too much more than the
Android source and build scripts. Windows probably requires some sort of
service to allow it to communicate with the buildmaster.

BuildBot:  http://buildbot.net/trac 

Hudson:  http://wiki.hudson-ci.org/display/HUDSON/Meet +Hudson

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com  |  http://twitter.com/commonsguy 

Android App Developer Training:  http://commonsware.com/training.html 

--~--~---------~--~----~------------~-------~--~----~



Want to help with Android nightly builds?

by Fred Grott » Sun, 12 Apr 2009 23:13:18 GMT


 Hudson has a an Android client to monitor :)








--~--~---------~--~----~------------~-------~--~----~



Want to help with Android nightly builds?

by Fred Grott » Sun, 12 Apr 2009 23:50:30 GMT


 I may become involved..it depends upon success of an ongoing
business/project gig discussion  that I am currently in with a startup..
The start up  at some point would be relying upon those nightly builds.

How different is the build scripts/receipes from bitbake?








> 



Want to help with Android nightly builds?

by Mark L. Chang » Tue, 14 Apr 2009 01:01:05 GMT


 



Mark, I'm for sure down for doing #1. I can also run #2 if it makes
sense. I just have zero experience doing this, but have plenty of
boxen at my disposal to run stuff. We should chat offline. You have my
email.

--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Error While booting Android_2.2_r1.1

Hi I successfully compiled 2.2_r1.1 for my ARM9 processor. I got
root ,data,system folder after compilation. When I copied file system
on SD-card My kernel boots fine but I at zygote its giving error as
follows..

init: starting 'console'
init: starting 'servicemanager'
init: starting 'vold'
init: starting 'netd'
init: starting 'de{*filter*}d'
init: starting 'ril-daemon'
init: starting 'zygote'
init: starting 'media'
init: starting 'dbus'
init: starting 'installd'
init: starting 'keystore'
init: command 'class_start' r=0
init: processing action 0x2b488
(property:persist.service.adb.enable=1)
init: starting 'adbd'
init: command 'start' r=0
sh: can't access tty; job control turned off
# init: Created socket '/dev/socket/vold' with mode '660', user '0',
group '1009'
init: Created socket '/dev/socket/netd' with mode '660', user '0',
group '1000'
init: Created socket '/dev/socket/rild-debug' with mode '660', user
'1001', group '1000'
init: Created socket '/dev/socket/zygote' with mode '666', user '0',
group '0'
init: Created socket '/dev/socket/rild' with mode '660', user '0',
group '1001'
init: Created socket '/dev/socket/dbus' with mode '660', user '1002',
group '1002'
init: Created socket '/dev/socket/installd' with mode '600', user
'1000', group '1000'
init: Created socket '/dev/socket/keystore' with mode '666', user '0',
group '0'
init: waitpid returned pid 852, status = 00000000
warning: `zygote' uses 32-bit capabilities (legacy support in use)
init: waitpid returned pid 848, status = 00000009
init: process 'zygote', pid 848 exited
init: process 'zygote' killing any children in process group
init: service 'media' is being killed
init: starting 'media'
init: waitpid returned pid 849, status = 0000000f
init: untracked pid 849 exited
init: starting 'zygote'
init: Created socket '/dev/socket/zygote' with mode '666', user '0',
group '0'
init: waitpid returned pid 911, status = 00000009
init: process 'zygote', pid 911 exited
init: process 'zygote' killing any children in process group
init: service 'media' is being killed
init: starting 'media'
init: waitpid returned pid 910, status = 0000000f
init: untracked pid 910 exited
init: starting 'zygote'
init: Created socket '/dev/socket/zygote' with mode '666', user '0',
group '0'
init: waitpid returned pid 926, status = 00000009
init: process 'zygote', pid 926 exited
init: process 'zygote' killing any children in process group
init: service 'media' is being killed
init: starting 'media'
init: waitpid returned pid 925, status = 0000000f
init: untracked pid 925 exited
init: starting 'zygote'
init: Created socket '/dev/socket/zygote' with mode '666', user '0',
group '0'
init: waitpid returned pid 941, status = 00000009
init: process 'zygote', pid 941 exited
init: process 'zygote' killing any children in process group
init: service 'media' is being killed
init: starting 'media'
init: waitpid returned pid 940, status = 0000000f
init: untracked pid 940 exited
init: starting 'zygote'
init: Created socket '/dev/socket/zygote' with mode '666', user '0',
group '0'
init: waitpid returned pid 956, status = 00000009
init: process 'zygote', pid 956 exited
init: process 'zygote' killing any children in process group
init: service 'media' is being killed
init: starting 'media'
init: waitpid returned pid 955, status = 0000000f
init: untracked pid 955 exited
init: starting 'zygote'
init: Created socket '/dev/socket/zygote' with mode '666', user '0',
group '0'

The zygote is looping and always giving "untracked pid ... exited "

Please help me as i got stuck for 2-3 days. any hint or suggestion is
appreciated.
Thanks in advance.

-- 

2. APK abbreviations

hi .this is my first Post . i very happy share my doubts wit
u.........


What is the abbrevation of the APK  in android ?


 how can we extract apk file ?

-- 

3. (Updated) WTS: Motorola Defy 2nd (blm genep 1minggu)

4. How to make webview answers onmousedown immediataly when touched?

5. Twitter ERROR 401 Authentication credentials are missing

6. Android Emulator and Proxy

7. Epic 4G, Galaxy Tab, and Transform Updates for Sprint