excluding unchanged binaries from checkin

[kozchris]

Hello,

I have an automated (final builder) process that does the following,

1) checks out all the files in a directory
2) copies the latest versions of those files overwriting the checked out versions
3) does a checkin of the files with the command:

Running Vault with command line : commit -user "admin" -password "******" -host "10.100.0.66" -repository "eCommerce" -unchanged undocheckout "$/xxx/SiteData/themes/yyyy/"

There are a bunch of unchanged images files (.gif, .jpg) and these keep getting checked in. What is the correct command to skip checking in unmodified image files?

Thanks,
Chris

[lbauer]

What version of Vault are you using?

Are the unchanged files being checked in and incremented a version each time?

Looks like you're using the correct option:

Code: Select all

-unchanged checkin|leavecheckedout|undocheckout

Action to perform on an unchanged, checked-out file during commit.
Check the file in unmodified, leave the file checked out, or
undo the checkout of the file. The default is "undocheckout".

So the question is -- does Vault think these files have changed? Is the timestamp different than it was before?

[kozchris]

vault client is 5.1.1 (19215)
vault server is 5.1.0.19172

I performed the process manually with one of the image files. In the vault client the file is listed with details: "size unchanged" but with a type of "modified". Doing a diff says the files are identical using raw comparison.

Yes, the files are getting checked in and incremented with a new version each time according to the vault history.

Thanks for responding

[kozchris]

Any other ideas? Is there away to tell vault to ignore a time difference if that is what it is seeing.

[lbauer]

Vault compares the time stamp of the local file to the time stamp of the baseline file in the client-side cache. If it's different, Vault considers the file to be modified.

If files aren't being modified, you could get them by their modification date, which should remain constant, or perhaps the last checkin time. Use the -setfiletime option in the Command Line Client:

Code: Select all

-setfiletime checkin|current|modification

Sets the time of the local file.

checkin - use the last checkin time
current - use the current system time
modification - use the file's last modified time.