Difference between revisions of "Development Team/Buildbot"
(New page: We are running periodic builds of Sugar using the [http://buildbot.net buildbot] automation system. Full builds, which starts every time from a clean source and installation tree, are run ...) |
|||
| Line 1: | Line 1: | ||
| + | == Builds == | ||
| + | |||
We are running periodic builds of Sugar using the [http://buildbot.net buildbot] | We are running periodic builds of Sugar using the [http://buildbot.net buildbot] | ||
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 | ||
Revision as of 18:21, 3 August 2008
Builds
We 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 3 hours. The status of the builds is available through a web interface and failures are notified to the development mailing list.
Status
It gives you a time-oriented summary of recent buildbot activity, by showing a time-based chart of events. It provides detailed information about all steps of all recent builds, and provides hyperlinks to look at individual build logs. By simply reloading this page on a regular basis, you will see a complete description of everything the buildbot is currently working on.
It shows the last 20 builds performed by the buildbot, one line each. Each line is a link to detailed information about that build.
It shows the status of the latest build for each builder and allows to force or interrupt builds.
Master
The latest build master configuration is hosted in a git repository. The service is currently hosted on sugarlabs2.xen.prgmr.com and is administered by [[User::Marcopg]].
Slaves
fedora9
Hosted on sugarlabs2.xen.prgmr.com, administered by [[User::Marcopg]].
Contribute
You 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.
1. Setup a dedicated user account for the slave, usually named buildbot. 2. Run a sugar-jhbuild on it, make sure that it's passing the sanity check (all the depencies are installed) and the build succeed. 3. Install buildbot. 4. Run the buildbot command as follows. Name it by the distribution it's runned on, for example fedora9.
buildbot create-slave slave sugarlabs2.xen.prgmr.com:9989 SLAVENAME PASSWORD
5. Get in contact with [[User::Marcopg]] to setup the builders on the master.