Development Style - CVS does not detect changes?

[ajj3085]

I've been using Vault for a while now, and I've always used the VSS concurrent development style. I wanted to switch to CVS style, to eliminate the delay from when I start typing i a file until when its auto-checked out for me, and to be more consistent with how SVN works as that's what I use for my fulltime employment.

I also have CCNet running to do automated CI builds, and the output of all projects is compiled to a bin folder which is then committed on success. The build uses the same Vault logon as I do.

It seems that when I changed to CVS style, everything worked except that when the build when to commit Vault did an Undo checkout as if the files were unmodified. Changing the setting back to VSS style and forcing another build did work correctly and committed the changed binaries.

I'm assuming that because the files are of the unmergable type, Vault just assumed they hadn't changed instead of checking. Can this be resolved? I really would like to change to the VCS style.

[lbauer]

We use CVS mode with CCNET here and haven't encountered this issue.

Is the build running under the same logged in Windows user as you?

We'll do some testing here to see if we can reproduce this.

[lbauer]

We could use more information to try to reproduce this. Are you using the Vault Command Line Client with Cruise Control to commit the build's changes?

[ajj3085]

We could use more information to try to reproduce this. Are you using the Vault Command Line Client with Cruise Control to commit the build's changes?

No, I'm using the NAnt tasks to work with Vault from the build script.

[lbauer]

It's possible the NAnt tasks aren't using the Vault client-side cache, so the file status isn't being updated. I'll need to consult with our developers for more information about this.

[ajj3085]

It's possible the NAnt tasks aren't using the Vault client-side cache, so the file status isn't being updated. I'll need to consult with our developers for more information about this.

Thanks for looking into this. The odd thing is that it does work with VSS style; it only doesn't work for me using CVS style.

[lbauer]

We're still not sure why CCNet isn't detecting the modifications.

If you check out the files (while using CVS mode) then do the build, does that work?

Are the NAnt tasks running under your Vault user account?

Are they running under your Windows login?

Could you use a different Vault account, like Admin, to run the builds, and set that development style to VSS mode?

[ajj3085]

If you check out the files (while using CVS mode) then do the build, does that work?

No, it doesn't help. I actually didn't think this setting would affect the account on the build server, so i never changed the scrips, which do check out the files at the start of the build.

Are the NAnt tasks running under your Vault user account?

Yes, the scripts use my Vault user name and password

Are they running under your Windows login?

No, the CCnet server runs under a different domain account.

Could you use a different Vault account, like Admin, to run the builds, and set that development style to VSS mode?

I hadn't considered that; I thought since I only had one full license that I wouldn't be able to do that, but I'll give it a shot.