1. Ryan Creps
  2. PowerBuilder
  3. Monday, 17 December 2018

We are in a place in our project timeline where we can finally migrate to utilizing the new native SVN integration offered in PB2017 (specifically R3, LTS).  I've run into a few confusing setup requirements and trying to get clarification as to the intended approach.

When adding to source control, if I stage the workspace, target and application PBLs inside a current SVN checkout of the repository, it fails adding the files with an SVN error "... is already a working copy for a different URL".  The PB commit process doesn't see that the current folder is already a local checkout of the repository.

If I move the raw workspace to a folder outside the SVN checkout location, I'm able to initially add the workspace and files to source control.  I can SVN update from the original SVN checkout folder and get the newly committed workspace.  If I try to open the PB workspace from this location, I can open it using "Connect to Workspace" but none of the objects under PBLs are connected to their source.  

In nearly all other IDE environments, using GIT, SVN, or others, you can work directly on the local working copy of a repository.  It seems with PB native SVN, I can only do this if I start by connecting to the workspace from an external, dedicated location.  Is this intended?  Is this a bug, "not being able to deal with a checkout from a larger parent SVN working copy"?

Bear in mind that we work on a large enterprise system repository with multiple branches and many applications and components within the repository.  Having to handle PB in a separate structure is not ideal.

Thoughts and guidance appreciated!

-Ryan Creps

Ryan Creps Accepted Answer Pending Moderation
0
Votes
Undo

Is this similar in the GIT integration (admittedly not looked at this)? Is there any intention of being able to work in a checked out repository structure directly?

Comment
Hi Ryan,



GIT and SVN are implemented similarly on PowerBuilder. So yes, you can't work in a checked out repository structure directly. You may request an enhancement by opening a support ticket here: https://www.appeon.com/user/login?destination=/standardsupport/newbug



Regards,



Tom Jiang
  1. Tom Jiang
  2. Wednesday, 19 December 2018
There are no comments made yet.
  1. Wednesday, 19 December 2018
  2. PowerBuilder
  3. # 1
Tom Jiang Accepted Answer Pending Moderation
0
Votes
Undo

Hi Ryan,

You observation is correct. Currently the SVN implementation on PowerBuilder only works when the repository is initiated by itself. 

So after you use PB > Add to source control, instead of going to your original SVN checkout folder, you are expected to use PB > Connect to workspace, to checkout the workspace to an empty folder. This is how you set up for a new developer after setting us the SVN.

Of course, for yourself, you can just use the folder where you did PB > Add to source control, to continue your development. 

Regards,

Tom Jiang

Comment
There are no comments made yet.
  1. Tuesday, 18 December 2018
  2. PowerBuilder
  3. # 2
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies. Learn More