Author Topic: All packages have lost Version Control setting! (Read 8102 times)

mpolo · « **on:** July 19, 2005, 01:11:27 pm »

Hello all,

This is the second time this has happened, where for some unkown reason, all packages under source control suddenly have their 'Version Control' dropdown set to (None).

It was working perfectly for months up until last week and now twice inside of 6 days.... Any idea of what could cause this? At first I thought someone deleted and recreated all version configs, but now this is not likely as I warned them not to touch this area of EA.

Any ideas? Where is this information stored (I am running the respository off of SQL Server)

Thanks!

Michael

Rob_M · « **Reply #1 on:** July 19, 2005, 04:34:43 pm »

I lost some settings (not version control) right after an EA upgrade to 768.

Might it be this?

Rob M

mpolo · « **Reply #2 on:** July 20, 2005, 06:47:22 am »

Thanks for the response Rob,

That may have been possible but I just tried the upgrade and it did not remove my re-connected packages....

If anyone knows where this setting is kept (I checked the t_package table and it does not seem to be kept there), please let me know.

Michael

TrtnJohn · « **Reply #3 on:** July 20, 2005, 11:39:54 am »

Are you using SourceSafe??

I've had this exact problem and haven't found any resloution myself. Other than going into every package and manually reseting it. (painful!)

mpolo · « **Reply #4 on:** July 21, 2005, 11:15:13 am »

We're using SourceGear's Vault Version Control Software.

Right now we have around 30 packages in about 5 configurations, it's a pain to have to reconnect them when this happens (only twice so far).

Hopefully someone can figure out why this is happening.

Michael

khanabdulr · « **Reply #5 on:** July 22, 2005, 12:05:09 pm »

Does Sparx System support using Vault as the Version Control package

We are looking at using Vault but not sure if Sparx System supports it.

mpolo · « **Reply #6 on:** August 04, 2005, 07:00:57 am »

Vault integration used to be not so good (used to have to manually check in and out in vault client), but in recent releases, it has gotten much better.

That being said, I don't think they test Vault source control with each new release, so you may run into problems when you install client patches.

BTW, I received an email from support on this issue and the patch will be in build 769.

Michael

rswelker · « **Reply #7 on:** September 06, 2005, 08:00:29 pm »

Anyone know whether the fix made it into build 769? I don't see it clearly listed but I could be missing it.

HowardB · « **Reply #8 on:** September 06, 2005, 10:30:31 pm »

The problem you are observing is due to a bug that was exposed in build 768, after removing invalid VCConfigs from the list of available configs. This bug was rectified in build 769, however the release notes do not reflect this. My apologies for this oversight.

EA supports all SCC compliant version control products, including SourceGear Vault.

Of all the SCC products that we test with, we probably use Vault the most.

The only thing to watch out for, is in the Vault dialog, where you specify the Project folder. I have noticed that on occasion, the lowest folder name is repeated in the Project pathname, which prevents EA from making the proper connection.

rswelker · « **Reply #9 on:** September 07, 2005, 05:06:18 am »

Thanks Howard. We'll give 769 a try

rswelker · « **Reply #10 on:** September 11, 2005, 01:01:54 pm »

That did the trick. Thanks again Howard.

brichardson · « **Reply #11 on:** April 07, 2006, 02:57:32 pm »

I had a similar issue. In addition, when I use a previous model as a new DB template it will inherit old DB SCC flags. What I did in both cases was write a Perl script, utilizing the Perl DBI to make a DB connection, modify the t_packages table and the specific field with the pertinent values.

Sparx Systems Forum

News: