Re: Fast way to get changed files since label?

Cool.  It's great when the features are already implemented.  You can 
actually get more detail (probably) by using the history command of the 
Vault command line client.  I think that we just let DateTime parse the 
string that you pass in, so you should be able to pass in a startdate 
with hours and minutes on it.  Alternatively, you can look at the 
History API example at:

http://support.sourcegear.com/viewtopic.php?t=450

-Jeremy


Jason Zisk wrote:

>Actually I found a great way to do this using the GUI, I was just going to
>post my results.  :)
>
>I found that if I simply use the history command, but set the "on or after"
>date to the day of the last build I can get a pretty clear picture of what
>files have changed.  It isn't 100% perfect though, which brings me to a
>feature request:
>
>I'd like the history's "on or after" date to be more accurate, like include
>the hour and minute.  If I can have it show me the history from August 15th
>5:15pm or after then I will have a list of all files that have changed since
>the exact time when the last build was made.
>
>If anyone sees any holes in this method let me know, but for this first
>patch I just made it seemed to work quite well.
>
>- Jason Zisk
>- nFusion Interactive LLC
>
>
>----- Original Message ----- 
>From: "Jeremy Sheeley" <[email protected]>
>To: "Jason Zisk" <[email protected]>
>Cc: <[email protected]>
>Sent: Wednesday, August 18, 2004 11:01 AM
>Subject: Re: [vault-list] Fast way to get changed files since label?
>
>
>  
>
>>Jason,
>>
>>You would have to use the client API to try to do something like this.
>>As a starting point, check out my blog on using the client API at
>>http://weblogs.asp.net/jeremy_sheeley
>>
>>For what you want to accomplish, you will need to compare the results of
>>a call to myClient.Connection.GetLabelStructureByName with the current
>>tree cache, which is accessed through the
>>myClient.TreeCache.Repository.Root object.  Give me an email off-list
>>and I'll help you with this (as long as you don't mind me creating a
>>blog article off our discussions).
>>
>>-Jeremy Sheeley
>>
>>
>>Jason Zisk wrote:
>>
>>    
>>
>>>Right now I'm in the unenviable position of having to make many small
>>>patches for a beta of a product we're working on.  What we do is we label
>>>each release, then when I need to make a patch I do a diff on the files
>>>      
>>>
>in
>  
>
>>>the repository vs. the last label.  This gives a nice listing of all the
>>>files that have changed, making my patch-making much easier.
>>>
>>>The problem is the speed.  It takes several hours to do this, I guess due
>>>      
>>>
>to
>  
>
>>>the number and size of our files that it needs to download (over the
>>>internet!).  I'm wondering if there is a faster way to use labels to see
>>>what has changed/what is new?  I don't care about the actual difference
>>>      
>>>
>_in_
>  
>
>>>the files, I just want to know which files.  It looks like vault is going
>>>overboard and actually downloading both version of the file and doing a
>>>      
>>>
>full
>  
>
>>>diff, when it could simply be doing a checksum check on each file to tell
>>>      
>>>
>me
>  
>
>>>if they are different.
>>>
>>>Hmm well you know I guess I could do the diff vs. the files on my HD,
>>>      
>>>
>maybe
>  
>
>>>eliminating half the download?  That could double the speed I guess but
>>>      
>>>
>it
>  
>
>>>would still take quite a while.  This set of files is around the 2
>>>      
>>>
>gigabyte
>  
>
>>>range.
>>>
>>>Really it takes so long and I have to make so many patches I may have to
>>>download a seperate program to do the actual directory diff, and just
>>>      
>>>
>keep a
>  
>
>>>version of the last build around on my HD so I can compare it to the
>>>      
>>>
>latest
>  
>
>>>version.  But I'm hoping I can just use vault to do this task.  :)
>>>
>>>- Jason Zisk
>>>- nFusion Interactive LLC
>>>
>>>
>>>_______________________________________________
>>>vault-list mailing list
>>>[email protected]
>>>http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list
>>>
>>>
>>>      
>>>
>
>
>_______________________________________________
>vault-list mailing list
>[email protected]
>http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list
>  
>