RE: Continuous Integration Question

We use the Cruise Control .net continuous integration server, from ThoughtWorks. All our code is in one subversion repository and all our projects, on cruise control, are built with NAnt scripts.

Each project has two items in cruise control. The first is the continuous build, this one is built every 20 minutes or so if there has been a change. Below is a summary of the script actions:
1. Update the local working copy with the latest changes from the repository.
2. Build the project.
3. Run unit tests, currently using NUnit.
4. Run features tests, currently using FitNesse.

If any of these actions fail then the build fails.

The second item for the project is a release build. This item is not scheduled it is developer initiated. When a project is ready for release this build does all the actions above, although debugging information is removed from the output, with the final step a svn copy to the projects Tags directory. We have plans to copy the project output to our web server for simple deployment.

If a build starts failing we give it priority and get it working again as soon as possible. It has also simplified our release process.

All in all I'd say we're pretty happy with our CI setup, although I can'ty speak for the other team members.
_________________________________________________________________
Keith Moore

-----Original Message-----
From: bruce [mailto:bedouglas_at_earthlink.net]
Sent: Friday, 17 October 2008 2:16
To: users_at_subversion.tigris.org
Subject: Continuous Integration Question

Hi.

In doing some research, I've come across various apps that deal with the concept of Continuous Integration/Software Production Management, which apparently is the process of being able to manage the process of creating/developing/building/testing/releasing projects/apps using repositories/build processes/etc... The CI/SPM process, also apparently allows for the implementation of workflow processes/procedures for managing the various apps/projects while being developed.

I've got a project in mind, that's going to require lots of little python apps that will need to be developed/built/tested/run multiple times, and to be recreated for each semester. (the apps deal with course schedules for colleges). Subversion would of course be the repository of choice, and since it appears that a number of the CI type of apps I've seen use SVN, I figured that I'd see if anyone here has actually used/implemented a CI/SPM system, and what your thoughts are.

Thanks

#####################################################################################
Attention:
The information contained in this message and or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact the sender and
delete the material from any system and destroy any copies.
#####################################################################################

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-17 04:50:05 CEST