1. David Vasconcelos
  2. PowerBuilder
  3. Monday, 26 August 2019 15:33 PM UTC

Our current version control system is antiquated and needs to be replaced.  I am giving subversion a try because I need to be able to have the capability to lock.  I followed the basic setup from Bruce's video and have the following questions/issues.

Environment: PowerBuilder 2017 R3, Windows server containing the Subversion Server and repository,  VisualSVN (free/non-licensed version) for server and TortoiseSVN for client.

 

1.  Did the "add to source" and completed the setup for the project.  While playing around I reset source control back to "None" on the properties of the workspace,  which removed subversion from the dropdown.  How do I reestablish the connection back to subversion?

2. Locking?  I have the original project in subversion, I then created a "working copy" i.e. "connect to workspace".  To test if I can see locking I went back to the original project and did a "get lock" then switched my workspace to the working copy.  It is not showing that the object is locked, so I did an update and still no change. Is there a configuration setting so that the Lock shows up on my working copy... did I miss a step?  If I tried to "get lock" from my working copy it does fail, it recognizes that the object is locked. 

 

 

David Edison Accepted Answer Pending Moderation
  1. Tuesday, 27 August 2019 01:50 AM UTC
  2. PowerBuilder
  3. # 1

#1. You can use "connect to workspace" but it will download everything from the server again. But here is a workaround. Let us say you have an existing repository in C:\MyWorkspace

1.       Temporarily rename you existing repository in another name C:\MyWorkspace_temp

2.       Create a new folder with the name C:\MyWorkspace

3.       Using “Connect to Workspace” to download the workspace from the Git/SVN server.

4.       Delete C:\MyWorkspace and rename C:\MyWorkspace_temp back to C:\MyWorkspace

#2. SVN works in offline mode. In other words, it does not have a constant connection to the server to refresh the status of every object until you do a commit or update. That’s part of the reason PB didn’t include this feature to indicate a lock on an object as it could be out of sync with the server without a constant connection.  

 

Comment
  1. David Vasconcelos
  2. Tuesday, 27 August 2019 16:06 PM UTC
Tom, regarding #2 is that only for the Native SVS? I have talked to others and they mentioned that when they did use subversion they did see a lock but that was with plugin source control vs Native SVS.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.