We are using Vault in a midsize project and have recognized some strange behaviors during getting the latest version.
Using “Get Latest Versionâ€
Get Latest Problems
Moderator: SourceGear
-
a.haytabay
- Posts: 3
- Joined: Fri Dec 16, 2005 3:32 am
Get Latest Problems
- Attachments
-
- message.txt
- The messages from the Message Tab
- (43.54 KiB) Downloaded 553 times
-
- A view of the project history
- vault.History.png (13.2 KiB) Viewed 3396 times
-
a.haytabay
- Posts: 3
- Joined: Fri Dec 16, 2005 3:32 am
The answer to your questions is not easy because of monitoring over 8000 files in over 1000 folders.
It occurs in differnet folders and files. We can not monitor it.
We see only that the build on the local machines is breaking after getting the latest version.
Does Vault provides any machanism to log the states of files and actions?
This will help us to find the information you ask for.
How trusty are the messages in the messages tab?
Does Vault get files without logging in the message tab or does Vault log files in the message tab which are not retrieved?
In most cases we do not know that we have not the latest version because the build on our local development machines is not breaking. If the build is breaking we can observe in some stages that the status is blank. Refreshing the view the status of some files will change to Old.
We have find out that calling twice get lattest will get all changes from Vault.
I hope that could be answerd a little bit of your questions.
Regards
Alper
It occurs in differnet folders and files. We can not monitor it.
We see only that the build on the local machines is breaking after getting the latest version.
Does Vault provides any machanism to log the states of files and actions?
This will help us to find the information you ask for.
How trusty are the messages in the messages tab?
Does Vault get files without logging in the message tab or does Vault log files in the message tab which are not retrieved?
In most cases we do not know that we have not the latest version because the build on our local development machines is not breaking. If the build is breaking we can observe in some stages that the status is blank. Refreshing the view the status of some files will change to Old.
We have find out that calling twice get lattest will get all changes from Vault.
I hope that could be answerd a little bit of your questions.
Regards
Alper
-
a.haytabay
- Posts: 3
- Joined: Fri Dec 16, 2005 3:32 am
More information about get latest
I take the time to monitor each get latest operation I made on my machine by
• performing get latest
• search for old and renegade files
• perform get latest again
And again I get a nice example of the Get Latest Issue. I have done a get latest on my machine this morning, which retrieved a number of files. Than start a search for files with the state “Oldâ€
• performing get latest
• search for old and renegade files
• perform get latest again
And again I get a nice example of the Get Latest Issue. I have done a get latest on my machine this morning, which retrieved a number of files. Than start a search for files with the state “Oldâ€
- Attachments
-
- message_20051223.txt
- (4.83 KiB) Downloaded 542 times
-
- vault.History_20051222.png (38.25 KiB) Viewed 3308 times
-
- vault.History_20051223.png (14.95 KiB) Viewed 3308 times
Interesting. Could you send me a copy of the Vault server log? It's sgvault.log and is in the %windir%\temp\sgvault directory on the Vault server. Make sure it includes the time period (adjusted for timezone difference, if any) of the gets:
[23.12.2005 09:44:48] to [23.12.2005 09:48:13]
Email the log to linda at Sourcegear.com. Please provide a link to this post in your email.
[23.12.2005 09:44:48] to [23.12.2005 09:48:13]
Email the log to linda at Sourcegear.com. Please provide a link to this post in your email.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager