[Mdarad-toolbox-devs] Continuous integration

[<fra...@po...>]

Hi,

I finally put in place the continuous integration process for=20
mdarad-genapp with cruisecontrol.=20

It has 2 running processes:

* "on checkin"  When someone checks in files, the process does the=
=20
following:
    - get latest version of sources
    - build application petstore
    - drop db, create db, create tables, init.sql for petstore
    - launch tests for petstore (kept in artifacts)
    - label mdarad-genapp in cvs: mdarad-genapp-<label number>

If something fails, the last person to checkin will be sent an email =
by=20
cruisecontrol (I will also receive this email).  The last person to=
=20
check in is responsible to fix the build.

* "weekly build". Every week (friday night) a build is launched that=
=20
much of the same as the "on check-in" process but a bit more....
    - get latest version of sources
    - build application petstore
    - drop db, create db, create tables, init.sql for petstore
    - launch tests for petstore (kept in artifacts)
    - code coverage for tests run on petstore (kept in artifacts)
    - memory and cpu profiling on petstore tests (kept in artifacts)
    - create a release (kept in artifacts)
    - label mdarad-genapp in cvs: mdarad-genapp-weeklybuild-<label nu=
mber>

This process is kept to build automatic weekly builds.  Right now I=
=20
don't think a nightly build is necessary so it will be done once a=
=20
week.  You can see the results here:

http://develapsetech.ca:8080/cruisecontrol

As you can see there are 2 projects.  One for the on checkin and the=
=20
other for the weekly build (wb suffix).  Look through the artfacts of=
=20
those 2 projects to better understand what is done.=20

If you have any questions or comments please post them on the list.  =
I=20
will try to create projects for mdarad-framework and=20
dataisland-primitives in a near future.

Fran=E7ois
  =20
  =20