"Renegade" files!

[jjonesBW]

Hello, the problem we are having here is while checking in files to update changes in vault but also keeping the files checked out, there are sometimes occurances of "renegade" files. Once a file has been labeled renegade it will not let us check an edited version in. Other users see the file as checked out.

How can we get rid of these "renegade" files? What causes them to be renegade files?

The program we are having this problem with is LabView 8.5 and we need to get this problem resolved ASAP!

Thanks.

Jon

[lbauer]

Are you trying to use LabView integrated with Vault? We haven't tested it and don't support it. Some unsupported IDE's do work with Vault, as they use the same integration API that Vault supports, but sometimes you get unexpected results.

A Renegade file is a file that is modified in the working folder but has not been checked out from the repository (or that Vault doesn't think is checked out).

There may be a problem with the calls that tell LabView to keep the file checked out.

If you open the Vault GUI Client, does the file appear to be checked out?

[jjonesBW]

Thanks for the prompt reply. When we use labview with vault we always have to open up the vault GUI to check files in and out. Currently from the vault GUI the renegade files appear to be checked out. So it appears that vault thinks the files have been checked out, then when they are modified the result is a renegade file which doesn't seem to be how things 'should' work. Based on your comments is sounds like it might be safer in the future to check the files in and check them back out in two steps rather than using the "check in but keep checked out" option? Also, how do we resolve this issue of the existing renegade files? We can't check in the file over the renegade file. Also, we've got version 3.5.1 of vault, are any of these issues addressed in a newer version of vault and how much would it cost to upgrade?

Thanks.

-Jon

[lbauer]

When you see renegade files, are you the person who has checked out the file?

File status is determined by info in each user's baseline files. Is more than one user using the same working folder? This can cause the status of files to be unpredictable. For instance if UserA and UserB have the same working folder, when UserA checks out a file and edits it, User B's file status will be Renegade because UserB doesn't have the file checked out.

If this doesn't explain the behavior you're seeing, send a screenshot to support at sourcegear.com, Attn: Linda.