1
edit
Changes
Created page with '<big><big> Continuous Integration Project - Buildbot</big></big> {{NexJ_Express Index}} ==Buildbot Resources== :The [http://buildbot.net/trac Buildbot] is a system to automate th…'
<big><big> Continuous Integration Project - Buildbot</big></big>
{{NexJ_Express Index}}
==Buildbot Resources==
:The [http://buildbot.net/trac Buildbot] is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure.[http://buildbot.net/buildbot/docs/current/Introduction.html#Introduction]
: [http://buildbot.net/buildbot/docs/current/index.html#Top Here] is the documentation for Buildbot. [https://developer.mozilla.org/presentations/buildbot-2.01.07.mov This video]also explains different features of this system.
:The buildmaster is usually fed Changes by some sort of version control system, which may cause builds to be run. As the builds are performed, various status messages are produced, which are then sent to any registered Status Targets.[[Image:Buildbot.png|thumb|none|widthpx|]]
:-Change Sources, which create a Change object each time something is modified in the VC repository. Most ChangeSources listen for messages from a hook script of some sort. Some sources actively poll the repository on a regular basis. All Changes are fed to the Schedulers.
:- Schedulers, which decide when builds should be performed. They collect Changes into BuildRequests, which are then queued for delivery to Builders until a buildslave is available.
:-Builders, which control exactly how each build is performed (with a series of BuildSteps, configured in a BuildFactory). Each Build is run on a single buildslave.
:-Status plugins, which deliver information about the build results through protocols like HTTP, mail, and IRC.
*Common Requirements
:At a bare minimum, you'll need the following for both the buildmaster and a buildslave:
:-Python: http://www.python.org Buildbot requires python-2.4 or later.
:-Twisted: http://twistedmatrix.com (Twisted is an event-driven networking engine written in Python and licensed under the MIT license.)
:Requirements for Buildmaster
:-sqlite3: http://pypi.python.org/pypi/pysqlite
::The sqlite3 package is required for python-2.5 and earlier (it is already included in python-2.5 and later, but the version in python-2.5 has nasty bugs)
:-simplejson: http://pypi.python.org/pypi/simplejson
::The simplejson package is required for python-2.5 and earlier (it is already included as json in python-2.6 and later)
:-Jinja2: http://jinja.pocoo.org/2
::Jinja2 is a general purpose templating language and is used by Buildbot to generate the HTML output.
{{NexJ_Express Index}}
==Buildbot Resources==
:The [http://buildbot.net/trac Buildbot] is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure.[http://buildbot.net/buildbot/docs/current/Introduction.html#Introduction]
: [http://buildbot.net/buildbot/docs/current/index.html#Top Here] is the documentation for Buildbot. [https://developer.mozilla.org/presentations/buildbot-2.01.07.mov This video]also explains different features of this system.
:The buildmaster is usually fed Changes by some sort of version control system, which may cause builds to be run. As the builds are performed, various status messages are produced, which are then sent to any registered Status Targets.[[Image:Buildbot.png|thumb|none|widthpx|]]
:-Change Sources, which create a Change object each time something is modified in the VC repository. Most ChangeSources listen for messages from a hook script of some sort. Some sources actively poll the repository on a regular basis. All Changes are fed to the Schedulers.
:- Schedulers, which decide when builds should be performed. They collect Changes into BuildRequests, which are then queued for delivery to Builders until a buildslave is available.
:-Builders, which control exactly how each build is performed (with a series of BuildSteps, configured in a BuildFactory). Each Build is run on a single buildslave.
:-Status plugins, which deliver information about the build results through protocols like HTTP, mail, and IRC.
*Common Requirements
:At a bare minimum, you'll need the following for both the buildmaster and a buildslave:
:-Python: http://www.python.org Buildbot requires python-2.4 or later.
:-Twisted: http://twistedmatrix.com (Twisted is an event-driven networking engine written in Python and licensed under the MIT license.)
:Requirements for Buildmaster
:-sqlite3: http://pypi.python.org/pypi/pysqlite
::The sqlite3 package is required for python-2.5 and earlier (it is already included in python-2.5 and later, but the version in python-2.5 has nasty bugs)
:-simplejson: http://pypi.python.org/pypi/simplejson
::The simplejson package is required for python-2.5 and earlier (it is already included as json in python-2.6 and later)
:-Jinja2: http://jinja.pocoo.org/2
::Jinja2 is a general purpose templating language and is used by Buildbot to generate the HTML output.
