I've got a continuous integration system set up between two servers, A and B. Basically, Draco.net checks out everything from SourceSafe on A, builds it and deploys it all to B. The main NAnt build script is in the root folder. Everything works fine here so VSS is not faulty (I think).
I've also got a smaller user script whose sole purpose it to check out the source and main build script and run it.
The relevant bits are
<property name="root.dir" value="D:\work\build"/> <property name="vss.db.dir" value="D:\work\vss\srcsafe.ini"/> <property name="vss.db.username" value="user"/> <property name="vss.db.password" value="password"/> <property name="vss.get.dir" value="${root.dir}\vss.get"/>
<target name="get-source-files"> <mkdir dir="${vss.get.dir}"/>
<!-- get source files --> <vssget localpath="${vss.get.dir}" dbpath="${vss.db.dir}" path="$/Branches/${build.branch.name}/${build.branch.version}" username="${vss.db.username}" password="${vss.db.password}"/>
<!-- get latest build file (not the one in the branch --> <call target="get-build-file"/>
</target>
We've just switched our "A" server to a new Win2k3 machine which hosts the VSS database. I copied the whole vss folder across, and our Visual Studio users and Draco.net have no problem with the new location.
But my user script now fails every time with this error (verbose debug mode in NAnt):
D:\work\build\CodeweaversUser.build(48,7): Failed to open database "D:\work\vss\srcsafe.ini".: NAnt.Core.BuildException: D:\work\build\CodeweaversUser.build(48,7): Failed to open database "D:\work\vss\srcsafe.ini". ---> System.IO.FileNotFoundException: The specified module could not be found. at NAnt.Contrib.Tasks.SourceSafe.BaseTask.Open() --- End of inner exception stack trace --- at NAnt.Contrib.Tasks.SourceSafe.BaseTask.Open() at NAnt.Contrib.Tasks.SourceSafe.GetTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run()
It makes no difference if I use NAnt-contrib 0.85rc-1 or rc-2.
I've also tried it with the VSS dir set to these: D:\work\vss\ D:\work\vss \\dev\work\vss\srcsafe.ini \\dev\work\vss\ \\dev\work\vss
I'm pretty sure it's not a permissions issue because I set up everyone to have full control of the whole hard drive!
Now here is the strange thing: if I map drive W on my local machine to D:\work on the dev server, I can run the script on my local machine across the network and vssget works fine!
Can anyone suggest what's going on? Maybe this is a Windows issue but our network admin is just as clueless as me!
Cheers Ashley Moran
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Nant-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nant-users
