Subject: RE: RE: [Ccnet-user] VSS modification history one day off!?!? - msg#00002

Previous Message by Date: click to view message preview

RE: bug in Vault.cs

Hello. >From the vault.exe v2.0.6 command line client: C:\Program Files\SourceGear\Vault Client>vault.exe help history <vault> <usage> SourceGear Vault Command Line Client Copyright (c) 2003 SourceGear Corporation. All Rights Reserved. usage: vault.exe HISTORY [options] repositorypath HISTORY will display all committed actions to a file or folder in the repository specified by repositorypath. Server and authentication information is specified by: -host host Hostname of the vault server to connect to - also see SERVER -ssl Enables SSL for server connection -user username Username to use when connecting to server - also see USERNAME -password password Password to use when connecting to server -repository repositoryname Repository to connect to This is a list of possible options: -rowlimit limitnumber Limits the number of rows returned for a history query to limitnumber -datesort [asc | desc] Sort the history results in ascending or descending date order. -begindate local date [ time] Date to begin history at -enddate local date [ time] Date to end history display at -norecursive Do not act recursively on folders </usage> <result success="yes" /> </vault> I would think the "more correct" way is to use what is documented. Most of the time I see the following error in my ccnet.log file: 3/1/2005 9:35:03 AM: [Project:Warning]: Process timed out: c:\program files\sourcegear\vault client\vault.exe history "$/Project" -host "host" -user "user" -password "password" -repository "repository" -rowlimit 0. Process id: 1488. This process will now be killed. 3/1/2005 9:35:03 AM: [Project:Debug]: Process stdout: 3/1/2005 9:35:03 AM: [Project:Debug]: Process stderr: 3/1/2005 9:35:03 AM: [Project:Warning]: The timed out process has been killed: 1488 3/1/2005 9:35:04 AM: [Project:Error]: Exception: Source control operation has timed out. ---------- ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation has timed out. at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execu te(ProcessInfo processInfo) in d:\sourceforge\ccnet\project\core\sourcecontrol\ProcessSourceControl.cs: line 49 at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.GetMo difications(ProcessInfo info, DateTime from, DateTime to) in d:\sourceforge\ccnet\project\core\sourcecontrol\ProcessSourceControl.cs: line 38 at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vault.GetModifications(Dat eTime from, DateTime to) in d:\sourceforge\ccnet\project\core\sourcecontrol\Vault.cs:line 55 at ThoughtWorks.CruiseControl.Core.Project.GetSourceModifications(IIntegrat ionResult result) in d:\sourceforge\ccnet\project\core\Project.cs:line 185 at ThoughtWorks.CruiseControl.Core.Project.AttemptToRunIntegration(IIntegra tionResult result) in d:\sourceforge\ccnet\project\core\Project.cs:line 163 But sometimes I see the following error: 3/1/2005 11:59:55 AM: [Project:Error]: Exception: Source control operation failed: . Process command: c:\program files\sourcegear\vault client\vault.exe history "$/Project" -host "host" -user "user" -password "password" -repository "repository" -rowlimit 0 ---------- ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation failed: . Process command: c:\program files\sourcegear\vault client\vault.exe history "$/Project" -host "host" -user "user" -password "password" -repository "repository" -rowlimit 0 at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execu te(ProcessInfo processInfo) in d:\sourceforge\ccnet\project\core\sourcecontrol\ProcessSourceControl.cs: line 53 at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.GetMo difications(ProcessInfo info, DateTime from, DateTime to) in d:\sourceforge\ccnet\project\core\sourcecontrol\ProcessSourceControl.cs: line 38 at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vault.GetModifications(Dat eTime from, DateTime to) in d:\sourceforge\ccnet\project\core\sourcecontrol\Vault.cs:line 55 at ThoughtWorks.CruiseControl.Core.Project.GetSourceModifications(IIntegrat ionResult result) in d:\sourceforge\ccnet\project\core\Project.cs:line 185 at ThoughtWorks.CruiseControl.Core.Project.AttemptToRunIntegration(IIntegra tionResult result) in d:\sourceforge\ccnet\project\core\Project.cs:line 163 ---------- Just for reference, Draco.NET has the repository path as the last argument. I did receive the "A database error has occurred (FailDBFault)" error when running this command in a command prompt. After moving the repository path to the last argument, it started to work. But most of the time it actually works without errors. That is why I indicated the issue as being a bug. As a side note, I did notice that including the repository path as the last argument produces faster results. In either case, I wonder if I can increase the timeout period when the CC.NET service attempts to get recent modifications from vault. -Rami -----Original Message----- From: ccnet-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx [mailto:ccnet-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx] On Behalf Of Mike Roberts Sent: Monday, February 28, 2005 9:13 PM To: ccnet-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx Subject: Re: [Ccnet-devel] RE: bug in Vault.cs On Tue, 1 Mar 2005 10:12:32 +1300, Mike Roberts <mike.b.roberts-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote: > On Mon, 28 Feb 2005 07:49:35 -0800, Rami AbuGhazaleh <Rami-lOa8y9J0lkZWk0Htik3J/w@xxxxxxxxxxxxxxxx> wrote: > > > > I just installed SourceGear Vault Client v2.0.3 and the vault.exe > > history command syntax indicates that the repository path should be > > the last argument. > > > > I do not have an earlier version to install, but I think that is the > > same syntax since the first version. After follow-up from SourceGear support, it seems that CruiseControl.NET is already doing the right thing, and it should work with 2.0.6 http://support.sourcegear.com/viewtopic.php?p=12105#12105 Rami - my suggestion is that you follow up with SourceGear since it looks like you must have some other problem. You'll probably want to give a command-line example rather than any CruiseControl.NET output. Mike ------------------------------------------------------- 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 _______________________________________________ Ccnet-devel mailing list Ccnet-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ccnet-devel ------------------------------------------------------- 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_ide95&alloc_id396&op=click

Next Message by Date: click to view message preview

Re: RE: bug in Vault.cs

On Tue, 1 Mar 2005 12:27:58 -0800, Rami AbuGhazaleh <Rami-lOa8y9J0lkZWk0Htik3J/w@xxxxxxxxxxxxxxxx> wrote: > As a side note, I did notice that including the repository path as the > last argument produces faster results. In either case, I wonder if I > can increase the timeout period when the CC.NET service attempts to get > recent modifications from vault. That would be a relatively simple change. It would require a 'timeout' element to be added to Vault's configuration and a change to Vault.CreateHistoryProcessInfo() to set the TimeOut property of the ProcessInfo. If a TimeOut has not been set on the configuration, CCNet's default timeout should be used. I've added this to Jira as http://jira.public.thoughtworks.org/browse/CCNET-353 . Mike ------------------------------------------------------- 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

Previous Message by Thread: click to view message preview

Re: RE: bug in Vault.cs

On Tue, 1 Mar 2005 10:12:32 +1300, Mike Roberts <mike.b.roberts-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote: > On Mon, 28 Feb 2005 07:49:35 -0800, Rami AbuGhazaleh > <Rami-lOa8y9J0lkZWk0Htik3J/w@xxxxxxxxxxxxxxxx> wrote: > > > > I just installed SourceGear Vault Client v2.0.3 and the vault.exe history > > command syntax indicates that the repository path should be the last > > argument. > > > > I do not have an earlier version to install, but I think that is the same > > syntax since the first version. After follow-up from SourceGear support, it seems that CruiseControl.NET is already doing the right thing, and it should work with 2.0.6 http://support.sourcegear.com/viewtopic.php?p=12105#12105 Rami - my suggestion is that you follow up with SourceGear since it looks like you must have some other problem. You'll probably want to give a command-line example rather than any CruiseControl.NET output. Mike ------------------------------------------------------- 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

Next Message by Thread: click to view message preview

RE: RE: [Ccnet-user] VSS modification history one day off!?!?

Is it supposed to be "hh:mm:ss" or "hh:nn:ss" (m is a placeholder for month in .NET I think). -----Original Message----- From: ccnet-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx [mailto:ccnet-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx] On Behalf Of Graham Tackley Sent: Wednesday, March 02, 2005 3:53 AM To: ccnet-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx Subject: RE: [Ccnet-devel] RE: [Ccnet-user] VSS modification history one day off!?!? We had exactly the same problem with the latest ccnet code a couple of weeks ago. We found that if we had customised the system time format (to "h:mm:ss tt") in control panel, vss did not recognise the time portion of the date time supplied when the date time contained seconds. Which effectively means that it doesn't report today's modifications as the "to" time is seen as midnight in the morning today. When we reset the control panel format to standard UK format, it worked fine. This was more a problem with vss than ccnet, but owen if you do any more work on ccnet-319 make sure you check with a customised control panel date format ;) g > -----Original Message----- > From: ccnet-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx > [mailto:ccnet-devel- > admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx] On Behalf Of > exortech-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx > Sent: 24 February 2005 19:35 > To: ccnet-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx > Subject: Re: [Ccnet-devel] RE: [Ccnet-user] VSS modification history one > day off!?!? > > > And if I manually run it from the command prompt it works (correctly > > returns a list of modifications). But the server is still saying "No > > Modifications Detected." > > eric, > thanks for testing this. this does seem strange considering that > ccnet is only executing that command and parsing the results. i tried > something similar against my local repository with the current build > and it seemed to work. > i've checked in a new version (the forthcoming build 781) where i've > added logging of all output from the process streams. however, in > doing so, i also reduced the default logging level to info from debug. > so this means that you will need to change the logging level in your > ccnet.exe.config file to 4. > cheers, > owen. > ------------------------------------------------------- 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 _______________________________________________ Ccnet-devel mailing list Ccnet-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ccnet-devel This Message Scanned for Viruses by McAfee WebShield . ------------------------------------------------------- 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_ide95&alloc_id396&op=click