SourceGear Support

Good afternoon all, Using v3.5.0. We just completed a 40+ hour import process; I can log in from various clients and see all of the files I'm expecting, but when I click finish on the last dialgo of the SS Import Tool's wizard I get a popup asking me to confirm if I wish to cancel the import process...

Greetings! Using v3.5.0. We've got about a dozen repositories, divvied up mainly by engineering teams and the products they work on. When I add new users, they seem to by default get added as active users in all repositories. Is there a way to toggle this to do the opposite (I'd rather have to manua...

Much obliged!

Greetings! We're on v3.5.0. Been reading all I could find about the import/export utility that came out with 3.5.0, but I can't seem to find it to do some experiments. Is it in the Client? The Admin Tool? A seperate download? Couldn't find any reference to it in the help files either. Thanks! --jdav...

Oh, OK. We should be fine then. I dropped a test one a few weeks ago bigger than any I've going now and it was just a few minutes. Thanks!

Given what's in the active repositories, it wouldn't be a tremendous loss if they had to be scrapped; we would just generate and save some key history reports before doing so. I'm curious, though--What do you mean by "Dropping entire test repositories shouldn't be too much of a problem " ?...

This thread brought to light a question I had about our upcoming conversion to production: I've created about a dozen repositories thus far. A few are still empty and awaiting imports, 2 are for testing purposes, and 3 at the moment are actively used and we had no plans to scrub them. We were planni...

Thanks for the info!

I'll throw the check for the empty changeset into my build script to get the info I'm looking for.

Thanks for the feature request; I envision using that not just upon checkins, but for overall repository health checks as well.

Cheers,

--jdavidi

Greetings! Using v3.5. We have an automated build script utilizing the Vault command line that, after determining if a change has taken place in a folder, checks out a file, updates a compatibility string, and then checks the file in. The file checks out fine: <vault> <!-- Checked out: $/lti/dev/tra...

Not really, unless there's a way to use the import tool from command with a silent option...? Then it would be the diff between the start time and the first log entry. But nothing seems to get written to the import log until you've paged through the rest of the wizard following the pre-scan, and I j...

Using VSS Import 3.5.0... For about 3 years now, we've shared files in VSS when we split the tree for new versions, and have typically branched the files on an as-needed basis. When we convert everything to Vault, we're considering doing away with sharing altogether and making use of the Merge tools...

The import log itself was created yesterday when the pre-scan began, but remained blank until I began the import proper itself (the first few lines have this morning's date on them and signify the start of the export).

Greetings! Using VSS Import Tool 3.5.0 - I'd kicked off a VSS import attempt yesterday at 9:29 AM EST, and the pre-scan finished at some point after I left for the day. I was just curious if there was a log file/db entry that could give me a metric on how long the pre-scan itself takes? If it at all...

Wonderful; thanks for the quick responses!

An update: I just sent myself a few more emails and I am able to see these details (great stuff!) for these more recent transactions. I think I just found how to reproduce it: I have turned Required Check in comments ON. If a check out comment is supplied, but a check in comment is not, Vault accept...