The Design of Software (CLOSED)

A public forum for discussing the design of software, from the user interface to the code architecture. Now closed.

The "Design of Software" discussion group has been merged with the main Joel on Software discussion group.

The archives will remain online indefinitely.

Build process and continous integration

I am looking for some guidance on implementing build process.We have a SVN repository,and also setup cruisecontrol.net.The only thing CCI server does is,every time someone checks in,it builds and reports success/failure.
I want to build upon this on CCI server-add target for running unit tests,add script to run deployment.What are some other good practices?
anon
Friday, August 10, 2007
 
 
We do all of the above plus check for code coverage (http://emma.sourceforge.net/) and code format.
bob, from accounting Send private email
Friday, August 10, 2007
 
 
Our Parabuild at http://www.viewtier.com/parabuild.htm may worth a look. It is a software build and release managements system. Parabuild does a lot more then continuous integration.

Even if you are not in for a commercial system, you may check our free articles on software build automation management at http://www.viewtier.com/support.htm

Please feel free to ask questions, I'll be happy to help.

Regards,

Slava Imeshev
Slava Imeshev Send private email
Friday, August 10, 2007
 
 
We had our unit tests generate a web-readable format, where the front page had a package by package summary (e.g. 85 tests passed, 3 tests failed) and you could drill down to details.  Packages that passed were green, ones that failed even one test were red.  (All done using Anthill.)

The developer who set this up had worked at a company where they had a computer sitting in the middle of the office pointing to the main web page, so that everyone would see almost immediately if someone broke the build.  I say almost immediately, because it rebuilt every hour on the hour or something like that.
Michael G Send private email
Saturday, August 11, 2007
 
 
I have some confusion--
Does cruisecontrol will also have script to build and deploy?
Also,what kind of build script should be used by developers-one which will compile solution and run tests only,or something more?
anon
Saturday, August 11, 2007
 
 
Anon, It seems you're using .NET. If you're using VS2005, you can modify the .csproj files directly (it is a MSBuild project under the hood) and add your own targets. If you're using an older version, you can think of creating an NAnt script.

BTW, I prefer Luntbuild [1] over Cruisecontrol: although it's java-based and a bit slow, the features it offers are very useful -- I especially like the project/schedule concept + the build management features.

Typically what we do is we set up multiple schedules for a project -- dev, test, qa, stable. The dev schedule is a continuous build schedule, while the others are all manual. For each build, we build installers and auto-deploy them to a different IIS Site. So, if a person from testing team has to "upgrade" to the latest version, a build from that schedule is fired. We also tie the version number to the schedules ie. in version a.b.c.d, d => dev #, c => test #, b => qa # and so forth (You can build very complex schemes using Luntbuild).

[1] http://luntbuild.javaforge.com/
Ashish Kulkarni
Sunday, August 12, 2007
 
 
anon,
if you are interested in having your cruisecontrol.net questions directly, i would recommend posting on the ccnet-user group: http://groups.google.com.ag/group/ccnet-user. posting here will only subject you to recommendations from competing product vendors rather than answer your ccnet questions directly.
cheers,
owen.
owen rogers Send private email
Sunday, August 12, 2007
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz