Exception Thrown on Checkin

[dmurty]

Hello,
We have recently switched over to the CVS style of vault. So we no longer check a file out, we edit and then commit changes to the server. This switch has gone very well, with one exception. We have an automated build that builds our installations for us. Before the switch this automated build would checkout the Installshield project and then check it in. The Installshield project file is an XML file with an extension of ism. When we switched over to the CVS style we stopped the automated build from checking out the project file. The only problem is that if the automated build does not make any changes to this project file it throws the following excpetion:

<error>
<exception>System.Exception: The current change set does not have any items for $/1 - Current Development/Installation/HealthCare Assistant Common/HSICommon.ism
at VaultClientIntegrationLib.ServerOperations.ProcessCommandCommit(String[] objectPaths, UnchangedHandler unchanged, Boolean keepCheckedOut, LocalCopyType localCopy, Boolean resolveMerge, ChangeSetItemColl& csicRemove)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)</exception>
</error>
<result>
<success>False</success>
</result>

The strange thing is that if I do this same thing with another file with an extension of vb, vbproj, cs, or csproj it does not throw this exception if there is no changes. Any ideas?

Thanks,
Damien

[lbauer]

We haven't had specific reports of this before.

Does the build work with no errors if HSICommon.ism is checked out but not modified?

What version of Vault are you using?

[dmurty]

Yes,

If I checkout the project file exclusively and then no changes are made and then check it in then there is no exception thrown. I are using 5.0.4.18845.

Thanks,

[lbauer]

When you're in CVS mode, can you confirm that the file is writable?

[dmurty]

Yes, the file is writable.

[lbauer]

We're not sure what the problem is here. Would there be a problem with checking out the file, even though you're using CVS mode? You can still checkout when using CVS mode.

[dmurty]

The only problem with checking out the files is that the act of checking out gets the latest version of the file before checking out. This is an issue on our build machine if we have already starting coding on the next version and need to rebuild. This was one of the main reasons for switching to the cvs mode. With the CVS mode we could rebuild and then any changes that the build made we could merge at a later time. But with checking out we always have to have the latest file.

Thanks,

[lbauer]

What about using the merge later option:

See Command Line Client help:
http://download.sourcegear.com/misc/vau ... m#CHECKOUT

-merge [automatic|later|overwrite]

The action to take when updating a local file with new content.

automatic* - attempt to merge changes from the server
later - do not overwrite an existing, modified file
overwrite - overwrite the local file with the server's file

Also, there an option in Commit to "keep checked out".