I'd agree with bob here.
If the developer doesn't commit their work and it doesn't show up in the
build it's their own fault.
Plus consider that the developer hasn't finished making changse to the
checked out file. forcing them to perform a checkin may cause a failed
build, and break anyone else who performs a checkout on that "forced
checkin"
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Bob Archer
Sent: Tuesday, March 18, 2008 10:29 AM
To: Vinod Nair; nant-users@lists.sourceforge.net
Subject: Re: [NAnt-users] <vssget> task
Your probably going to need to use the exec tag to run VSS. I assume there
is a command that will list locked files. If there is a locked file you can
fail the build.
However, why would you do this? Usually you just build with the most
recently commited files?
BOb
----------------------------------------------------------------------------
--
From: [EMAIL PROTECTED] on behalf of Vinod Nair
Sent: Tue 3/18/2008 9:37 AM
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] <vssget> task
Hi,
I've been trying to implement the <vssget> task of nantcontrib in my build
script to get the latest files from my VSS source. My requirement is as
below :
Whenever I generate a build, I should get the latest of all the files from
the VSS source and then generate a build. And if any single file is
checked-out by any user, then it should throw some message that a particular
file is checked-out and hence the build process should stop from there. I
researched a lot on this, but was unable to find a solution.
Can anyone help me in this task.
Thanks,
Vinod.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users