[Mdarad-toolbox-devs] Continuous integration

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

As soon as I have the tests working (all pass).  I will implement=
=20
CruiseControl (continuous integration tool) on mdarad. All test cases=
=20
are of course welcome. Since it is hard to test the code generation=
=20
before it is actually generated, I suggest that we do both the follow=
ing:

- generate as many tests as possible (a part of it is done today)
- make manual test cases for our functionalities that we can checkin=
=20
under petstore/srcTest (which we can include in the generator afterwa=
rds)

This implies that once cruise control is installed, there should be n=
o=20
check in without launching a manual call to a continuous integration =
ant=20
target (that I will complete)  that will
- Get mdarad-framework, mdarad-genapp, andromda-webapp, dataisland=
=20
primitives from RCS in empty folder (will delete it first)
- Recompile all
- Generate a petstore application
- Delete petstore database
- Create petstore database
- Populate petstore database
- Deploy petstore in Jboss (ear) and in tomcat (war)
- Launch all tests for petstore(generated and not) and other=20
applications if we ever have any :)

If any of these test fails, the developer should not check in his fil=
es=20
before fixing the problem.  For example, if a test fails, the develop=
er=20
which is about to check in must go correct this test before checking =
in.=20
Then he relaunches the complete build and reiterates all is succesful=
.

In addition to this, CruiseControl will launch this build every night=
. =20
If succesful (and it should always be), it will also generate a code=
=20
coverage report and label the version in CVS.  CruiseControl will als=
o=20
launch the build after checkins have been made (he waits 15 minutes o=
f=20
idle time to make sure all checkins are done).  This means that if=
=20
someone breaks the build, we will know quite quickly who (so he can f=
ix it).

Any comments? Objections?

I'll try to put this in place this weekend.

Fran=E7ois