Burgess, Michael wrote:
So................is this easily achievable in NAnt? One of the key problems at
the moment lies with not being able to control or configure what we churn out.
I want to set it up on a continual build process and be able to easily output a
specific build if one source file changes that only impacts one project,
rendering a full build a waste of time.
One of our big bottlenecks here is getting all the code from PVCS. Most of the
time, most of the code we get is unchanged. If there was a way to reduce this
it would be awesome. Configurability would be excellent too. Being able to
specify at run-time what I want would be superb.
I think I'd start with using CruiseControl.Net to fire off the continual
NAnt jobs. CruiseControl.Net is set up to monitor changes to specific
source code areas, and only start a job if something in that area has
changed. I've never used PVCS, so I don't know the details of setting
that up, but I'm sure there are others on the CruiseControl.Net mailing
list who can help.
Gary
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
