SoC geeklog2 continuous builds - Revision history

Dirk: outdated - added link to current list

2010-03-04T20:44:08Z

outdated - added link to current list

Jtraub: /* Further Reading */

2008-03-24T17:27:27Z

‎Further Reading

Jtraub: Added link to another Continious Integration tool

2008-03-24T17:16:04Z

Added link to another Continious Integration tool

Jtraub at 13:39, 19 March 2008

2008-03-19T13:39:43Z

Jtraub: Added project goals + some links to buil systems

2008-03-19T13:36:32Z

Added project goals + some links to buil systems

Tony at 02:22, 6 March 2008

2008-03-06T02:22:55Z

New page

<center>(Return to the main idea page for the [[Google Summer of Code]])</center>

== Incentive ==

Geeklog 2 is a sophisticated system. A balance between rich features and ease of use must be struck which places a high emphasis on quality. A big part of establishing quality is to implement testing as a core part of the project. Additionally, there are key parts to the Geeklog 2 that require special processing such as building the models (the "M" part of MVC). Geeklog 2 makes heavy use of Propel, an object relational mapper, to limit the amount of SQL a developer has to write and enhancements to Propel make it possible to isolate all SQL from the rest of the system.

Because of these and a number of other complexities having a system in place that polls SVN for changes, checks out the code, runs unit tests and produces builds (i.e. PEAR-installable packages) would take some of the time and complexity with getting a new version out and it forces testing to be an integral part of the system.

== Objective ==

* Research Open Source build tools such as Phing, Xinc and Cruise Control to provide continuous builds
* Establish the actual build process including
** Checking out code from SVN
** Running Unit tests
** Running regression tests
** Upon test failures notification of the development team
** Upon successful testing tagging the code and doing full builds

== Level of Difficulty ==

''Hard''

Continuous builds in PHP is a relatively new concept. A good candidate must be willing to push forward and trudge new ground in a developing area within the PHP community.

== Further Reading ==

* [http://phing.info/ Phing]
* [http://code.google.com/p/xinc/ Xinc]
* [http://http://cruisecontrol.sourceforge.net/ CruiseControl]

[[Category:Summer of Code]] [[Category:Development]]

← Older revision		Revision as of 20:44, 4 March 2010
Line 1:		Line 1:
−	~~<center>~~(~~Return to the main idea page~~ for the [[Google Summer of Code]]~~)</center>~~	+	This is an old project idea for our (now defunct) sister project, AptitudeCMS (aka Geeklog 2). This project outline is therefore only of historical interest and you can not apply for this project in future instances of the Google Summer of Code. Please see our [[Google Summer of Code\|ideas page]] for a current list of GSoC project ideas.
		+

	== Incentive ==		== Incentive ==

@@ Line 42: / Line 42: @@
 * [http://buildman.limb-project.com/ Buildman]
 * [http://en.wikipedia.org/wiki/Continuous_integration Continious Integration]
 [[Category:Summer of Code]] [[Category:Development]]

@@ Line 40: / Line 40: @@
 * [http://buildbot.net/ BuildBot]
 * [http://continuum.apache.org/ Continuum]
 * [http://en.wikipedia.org/wiki/Continuous_integration Continious Integration]
 [[Category:Summer of Code]] [[Category:Development]]

@@ Line 40: / Line 40: @@
 * [http://buildbot.net/ BuildBot]
 * [http://continuum.apache.org/ Continuum]
+* [http://en.wikipedia.org/wiki/Continuous_integration Continious Integration]
 [[Category:Summer of Code]] [[Category:Development]]

@@ Line 17: / Line 17: @@
 ** Upon test failures notification of the development team
 ** Upon successful testing tagging the code and doing full builds
 == Level of Difficulty ==
@@ Line 28: / Line 37: @@
 * [http://phing.info/ Phing]
 * [http://code.google.com/p/xinc/ Xinc]
-* [http://http://cruisecontrol.sourceforge.net/ CruiseControl]
+* [http://cruisecontrol.sourceforge.net/ CruiseControl]
 [[Category:Summer of Code]] [[Category:Development]]