Hi Jay, Good question - the answer is:- "No history entries were found for the item and version combination specified." Which is fair enough, however, when forcing the build, why does this act like a continuous build? (ie., do nothing if no changes since last scheduled run) I've tried adding <force> but to no avail. The problem remains - no workspace is created and nothing downloaded. I've skipped around the problem by manually creating the workspace and forcing the get, so the rest of the build is running ok. The background to this is simply - a reporting database which needs the main database during build - hence, I grab the main db from source, create it from sql, and then run the actual db build I want. b.t.w - yes you're correct, we have all our builds wrapped up in eg., <cb:define name="DatabaseBuild.Template"> templates - which includes a large block of derived values and settigns, makes our actual build definitions only a few lines - so far so good. thanks for your help! would you mind pasting a couple of examples of your working multi blocks? regards Andy
> Date: Wed, 22 Dec 2010 01:26:40 -0800 > Subject: [ccnet-user] Re: sourcecontrol - multi - vsts - not working > From: [email protected] > To: [email protected] > > Hi, > > I can't see where you set the value of $(TFSServer), but I assume > that's scoped higher in the config file...can you verify that manually > running the command: > > TF.exe history -noprompt -server:http://tfs:8080 "$/Delivery Connect > XXXX/Release Branches/ReportsDatabase/1.1/015/0" - > version:D2010-12-22T07:47:20Z~D2010-12-22T08:19:20Z -recursive - > format:detailed > > ...returns something on the command prompt? I've been successfully > running multi-source TFS for a few months though without the use of > preprocessor constants (running v1.6.7274.5 btw). > > Cheers, > Jay
