Firstly i'd like to congratulate you guys on a great product. We are running a rapidly expanding development team and now have SourceGear vault as the standard source control tool.
As a software team we run nightly builds of our product that incorporates any changes that have been made through the day and then this version gets pushed out to all our developers who then have the latest version of the product every morning.
When a change is made to the code and submitted to the core set, Cruise Control then automatically runs a build consolidating the changed code into the product.
CruiseControl allows us to see when the last build occured, and so narrows down a window for example if we wanted to search for where the code was broken.
The issue with Vault is the GET command in the cmd line interface does not allow for a GET between certain start and end dates. The time taken for the GET command to then action is far longer due to it being unable to utilise the vault cache that is stored onthe client.
This addition into Vault would be simple yet be of huge benefit to our team and no doubt many others. The setup could be very similar to the help history cmd that uses begin date and end date switches that allows the user to specify a date and time.
Please let me know if this addition could be an likely include
Cheers
Steve
cmd line interface
Moderator: SourceGear
This would be a good addition to the CLC, but this is the first request we've had for it, and we are trying to limit the number of items for the next release so we don't fall too far behind. I'll add it as a feature request though.
Note that you can always grab the CLC source and implement this on your own
Note that you can always grab the CLC source and implement this on your own
I think I'm confused as to what you mean about "GET between certain start and end dates." Other source control tools support getting by a single date (the version of the file that was latest at that date is retrieved), but I'm not familiar with using a range for get. Would all versions in that range be retrieved (maybe to different working folders)?
Shaw Terwilliger
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`
OK, I understand now. This operation wouldn't be too difficult to add to the CLC, but I don't think it will make Vault 2.1. You may be able to invoke the existing CLC to view history (with a date range query), parse the affected file paths and IDs from the XML, and then invoke the CLC to get them to a working folder.
Shaw Terwilliger
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`