Book a Demo

Author Topic: Trouble with perforce (p4) integration  (Read 3108 times)

ppietrus

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Trouble with perforce (p4) integration
« on: April 27, 2005, 11:11:49 am »

Hi,
I am evaluating Enterprise Architect, I have build 751 and most recent perforce client. When I try to connect to perforce (by going to Project->Version Control->Set Version Control Options), I can enter my perforce server data, hit save, SCC dialog comes up where I can successfully select perforce user and workspace, and then when I click Ok, I am getting an error message:
"Error While Initializing Version Control Provider: Failed to Open SCC project"

What gives? Couldn't find any logs anywere under Enterprice Architect subdirectory with more detailed info.

The perforce installation itself seems ok as I can successfully configure Together/J to use perforce using the same perforce SCC plugin.

Any clues?

Thanks,
Pawel




michael_rainwater

  • EA User
  • **
  • Posts: 53
  • Karma: +0/-0
    • View Profile
Re: Trouble with perforce (p4) integration
« Reply #1 on: May 02, 2005, 04:53:13 pm »
Did you set your local path?  This is one option I missed the first time I tried to set this up.

The text box is grey (which makes you think it is disable).  But you still click the "..." button and set the folder.  Then, you can click the "Save" button.

I use EA with P4 all the time.  You don't need to set the version control options unless you plan to version control your packages seperately.  EA lets you set version control options for each package.  Then, it handles exporting to XML and checking into P4, etc.  They've done a farily nice job with the integration.  But (like everything in EA) you have to get used to the user interface and where to find things.

ppietrus

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Trouble with perforce (p4) integration
« Reply #2 on: May 04, 2005, 01:18:00 pm »

Ok, problem solved!

Turns client spec name was simply too long! It needs to be really short 7 or 8 characters max.

Apparently there are some bugs on the line of EA to perforce SCC plugin communications as with longer client spec name everything worked perfectly with other tools going through the same plugin but EA was failing. Also at one point I got some error message listing my client spec name which was garbled (apparently some internal memory buffer corruption).

Pawel