Development Team/Buildbot: Difference between revisions

No edit summary
 
(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 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
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]. The service is currently hosted
on sugarlabs2.xen.prgmr.com and is administered by [[User::Marcopg]].


== Slaves ==
== Slaves ==


fedora9
See [[Infrastructure Team/Resources#Build_Bots]].
 
Hosted on sugarlabs2.xen.prgmr.com, administered by [[User::Marcopg]].


== Contribute ==
== Contribute ==
Line 37: Line 35:
easy to set one up.
easy to set one up.


1. Setup a dedicated user account for the slave, usually named buildbot.
* 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
* 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.
3. Install buildbot.
* Setup the slave. Name it by the distribution it's running on, including the architecture (ex. fedora9-x86_64).
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
  buildbot create-slave slave sugarlabs2.xen.prgmr.com:9989 SLAVENAME PASSWORD
cd slave
mv Makefile.sample Makefile
* Run the slave:
make start


5. Get in contact with [[User::Marcopg]] to setup the builders on the master.
* Get in contact with master administrator to setup the builders.