Re: [Mdarad-toolbox-devs] Re: Continuous integration

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

If you want to make sure you haven't broken anything before commiting=
=20
(recommended).  I suggest you get the project "cruisecontrol" from=
=20
mdarad cvs sourceforge.  Then, before doing a checkin, you do the fol=
lowing:

(from the cruisecontrol directory)
- modify the default.properties to satisfy your needs
- launch the ant task: ant -f build-mdarad-genapp.xml verify.before.c=
ommit

If all is succesful, you can check in your modifications.

The task will build petstore, drop the db, recreate it, init.sql and=
=20
launch the tests.

If you have any questions, please let me know,

Frank

Fran=E7ois Eric wrote:

> You might notice that the jmx consle is not activated, this is a=
=20
> normal behaviour for a remote access.  I don't want anybody to forc=
e=20
> builds.  To access the jmx console you must be locally on=20
> develapstech.ca.
>
>
> Fran=E7ois Eric wrote:
>
>> Hi,
>>
>> I finally put in place the continuous integration process for=20
>> mdarad-genapp with cruisecontrol.
>> 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 ema=
il=20
>> by cruisecontrol (I will also receive this email).  The last perso=
n=20
>> to check in is responsible to fix the build.
>>
>> * "weekly build". Every week (friday night) a build is launched th=
at=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=
=20
>> number>
>>
>> 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 t=
he=20
>> other for the weekly build (wb suffix).  Look through the artfacts=
 of=20
>> those 2 projects to better understand what is done.
>> If you have any questions or comments please post them on the list=
. =20
>> I will try to create projects for mdarad-framework and=20
>> dataisland-primitives in a near future.
>>
>> Fran=E7ois
>>   =20
>
>
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server.=
=20
> Download
> it for free - -and be entered to win a 42" plasma tv or your very o=
wn
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.p=
hp
> _______________________________________________
> Mdarad-toolbox-devs mailing list
> Mda...@li...
> https://lists.sourceforge.net/lists/listinfo/mdarad-toolbox-devs
>
>
>