Difference between revisions of "Development Team/Buildbot"

Latest revision as of 13:16, 31 January 2012

NOTE:
The content of this page is considered
DEPRECATED and OBSOLETE
It is preserved for historical research, along with its talk page.

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 2 hours. The status of the builds is available through a web interface and failures are notified to the development mailing list.

Status

Waterfall Display: 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.

Recent Builds: It shows the last 20 builds performed by the buildbot, one line each. Each line is a link to detailed information about that build.

Latest 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 sugar-buildbot git repository. The service is currently hosted on sugarlabs2.xen.prgmr.com and is administered by Marco Pesenti Gritti.

Slaves

See Infrastructure Team/Resources#Build_Bots.

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.

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).

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.

@@ Line 1: / Line 1: @@
+{{obsolete}}
+{{TOCright}}
 == Builds ==
@@ Line 4: / Line 6: @@
 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
+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.
@@ Line 10: / Line 12: @@
 == Status ==
-[http://buildbot.sugarlabs.org/waterfall Waterfall Display]
+;[http://buildbot.sugarlabs.org/waterfall Waterfall Display]
+: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 gives you a time-oriented summary of recent buildbot activity, by showing a
+;[http://buildbot.sugarlabs.org/one_line_per_build Recent Builds]
-time-based chart of events. It provides detailed information about all steps of
+:It shows the last 20 builds performed by the buildbot, one line each. Each line is a link to detailed information about that build.
-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.
-[http://buildbot.sugarlabs.org/one_line_per_build Recent Builds]
+;[http://buildbot.sugarlabs.org/one_box_per_builder Latest Build]
+:It shows the status of the latest build for each builder and allows to force or interrupt builds.
-It shows the last 20 builds performed by the buildbot, one line each. Each line
-is a link to detailed information about that build.
-[http://buildbot.sugarlabs.org/one_box_per_builder Latest 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
+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]. The service is currently hosted
-on sugarlabs2.xen.prgmr.com and is administered by [[User::Marcopg]].
 == Slaves ==
-fedora9
+See [[Infrastructure Team/Resources#Build_Bots]].
-Hosted on sugarlabs2.xen.prgmr.com, administered by [[User::Marcopg]].
 == Contribute ==
@@ Line 46: / Line 35: @@
 easy to set one up.
-. Setup a dedicated user account for the slave, usually named buildbot.
+* Setup a dedicated user account for the slave, usually named buildbot.
-. Run a sugar-jhbuild on it, make sure that it's passing the sanity check (all
+* Make a sugar-jhbuild on it, check that the build succeeds.
-the depencies are installed) and the build succeed.
+* Install buildbot, preferably version 0.7.7.
-. Install buildbot.
+* Setup the slave. Name it by the distribution it's running on, including the architecture (ex. fedora9-x86_64).
-. 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
+ cd slave
+ mv Makefile.sample Makefile
+* Run the slave:
+ make start
-. Get in contact with [[User::Marcopg]] to setup the builders on the master.
+* Get in contact with master administrator to setup the builders.