Difference between revisions of "Development Team/Buildbot"
(→Status) |
|||
(18 intermediate revisions by 10 users not shown) | |||
Line 1: | Line 1: | ||
+ | {{obsolete}} | ||
+ | {{TOCright}} | ||
== Builds == | == Builds == | ||
Line 4: | Line 6: | ||
automation system. Full builds, which starts every time from a clean source and | automation system. Full builds, which starts every time from a clean source and | ||
installation tree, are run every 12 hours. Quick builds, which are built | installation tree, are run every 12 hours. Quick builds, which are built | ||
− | incrementally from the last build source and installation tree, are run every | + | incrementally from the last build source and installation tree, are run every 2 |
hours. The status of the builds is available through a web interface and failures | hours. The status of the builds is available through a web interface and failures | ||
are notified to the development mailing list. | are notified to the development mailing list. | ||
Line 21: | Line 23: | ||
== Master == | == Master == | ||
− | The latest build master configuration is hosted in a | + | The latest build master configuration is hosted in a [http://dev.laptop.org/git?p=users/marco/sugar-buildbot;a=summary sugar-buildbot] git repository. The service is currently hosted on sugarlabs2.xen.prgmr.com and is administered by [[User:Marcopg|Marco Pesenti Gritti]]. |
− | [http://dev.laptop.org/git git repository | ||
− | on sugarlabs2.xen.prgmr.com and is administered by [[User | ||
== Slaves == | == Slaves == | ||
− | + | See [[Infrastructure Team/Resources#Build_Bots]]. | |
− | |||
− | |||
== Contribute == | == Contribute == | ||
Line 37: | Line 35: | ||
easy to set one up. | easy to set one up. | ||
− | + | * Setup a dedicated user account for the slave, usually named buildbot. | |
− | + | * Make a sugar-jhbuild on it, check that the build succeeds. | |
− | + | * Install buildbot, preferably version 0.7.7. | |
− | + | * Setup the slave. Name it by the distribution it's running on, including the architecture (ex. fedora9-x86_64). | |
− | |||
− | on, | ||
buildbot create-slave slave sugarlabs2.xen.prgmr.com:9989 SLAVENAME PASSWORD | buildbot create-slave slave sugarlabs2.xen.prgmr.com:9989 SLAVENAME PASSWORD | ||
+ | cd slave | ||
+ | mv Makefile.sample Makefile | ||
+ | |||
+ | * Run the slave: | ||
+ | |||
+ | make start | ||
− | + | * Get in contact with master administrator to setup the builders. |
Latest revision as of 13:16, 31 January 2012
BuildsWe are running periodic builds of Sugar using the buildbot automation system. Full builds, which starts every time from a clean source and installation tree, are run every 12 hours. Quick builds, which are built incrementally from the last build source and installation tree, are run every 2 hours. The status of the builds is available through a web interface and failures are notified to the development mailing list. Status
MasterThe latest build master configuration is hosted in a sugar-buildbot git repository. The service is currently hosted on sugarlabs2.xen.prgmr.com and is administered by Marco Pesenti Gritti. SlavesSee Infrastructure Team/Resources#Build_Bots. ContributeYou can contribute to the build and testing infrastructure by offering to host a slave on Linux distributions which are currently not covered. It's relatively easy to set one up.
buildbot create-slave slave sugarlabs2.xen.prgmr.com:9989 SLAVENAME PASSWORD cd slave mv Makefile.sample Makefile
make start
|