Development Team/Buildbot: Difference between revisions

(14 intermediate revisions by 10 users not shown)

Line 1:

== 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 25:

Line 27:

== Slaves ==

~~{| border="1" cellpadding="10" cellspacing="0"~~

See [[Infrastructure Team/Resources#Build_Bots]].

~~!Name~~

~~!Host~~

~~!Admin~~

|-

~~|fedora9~~

~~|sugarlabs2.xen.prgmr.com~~

|[[~~User:Marcopg|Marco Pesenti Gritti~~]]

|}

== Contribute ==

Line 42:

Line 36:

* 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 the depencies are installed) and~~ the build ~~succeed~~.

* Make a sugar-jhbuild on it, check that the build succeeds.

* Install buildbot.

* Install buildbot, preferably version 0.7.7.

* Setup the slave. Name it by the distribution it's ~~runned~~ on, ~~for example~~ fedora9.

* 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

@@ 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 25: / Line 27: @@
 == Slaves ==
-{| border="1" cellpadding="10" cellspacing="0"
+See [[Infrastructure Team/Resources#Build_Bots]].
-!Name
-!Host
-!Admin
-|-
-|fedora9
-|sugarlabs2.xen.prgmr.com
-|[[User:Marcopg|Marco Pesenti Gritti]]
-|}
 == Contribute ==
@@ Line 42: / Line 36: @@
 * 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 the depencies are installed) and the build succeed.
+* Make a sugar-jhbuild on it, check that the build succeeds.
-* Install buildbot.
+* Install buildbot, preferably version 0.7.7.
-* Setup the slave. Name it by the distribution it's runned on, for example fedora9.
+* 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