• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Switch existing PB code to SVN coming from (PushOK+SVN)

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Switch existing PB code to SVN coming from (PushOK+SVN)

  1. Advice
0
Votes
Undo
  1. Thorsten Kummer
    Thorsten Kummer
  2. PowerBuilder
  3. Wednesday, 22 June 2022 08:16 AM UTC

Dear all,

 

we're using PowerBuilder (2019 R2)  along with the PushOK SVN bridge to access our SVN system.

We need to switch over now to eliminate the PushOK software to connect directly to SVN (Git is not an option currently).

- Would this need a new empty SVN repository? Or can we connect to our existing one. The examples I have seen so far did create new repositories.

- Should we wait for PB 2022 which contains some improvements? As far as I understood Armeen in earlier posts we will need at least 2019 R3 to make use of the locking feature which is essentla for us.

- are there any dos and dont's to consider?

 

Thanks in advance for your input.

Best regards

Thorsten

 

 

 

How to disable doubleclicked event in Ancestor dw?
Troubleshooting OLEObject
Responses (3)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 22 June 2022 15:12 PM UTC
  2. PowerBuilder
  3. # 1

Hi Thorsten,

You should be able to use existing repository.  If you are getting specific error when you do so, please make separate post about that detailing the error and the steps you followed.

PB 2019 R3 should be good minimum version for you to use.  There are some enhancements for SVN in PB 2022, but those are minor.  However, if you think your project would benefit from the other new features of PB 2022 then might be worth the jump: https://docs.appeon.com/pb/whats_new/New_Features_2022.html

Best regards,
Armeen

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 22 June 2022 17:10 PM UTC
Hi Thorsten;

In addition to Armeen's comment ...

FYI: The SVN/Git client that has been fully tested to work is: SVN client 1.9.7 and later.

What SVN version are you using?

Regards ... Chris
  1. Helpful
There are no comments made yet.
Bruce Armstrong
Bruce Armstrong Accepted Answer Pending Moderation
  1. Thursday, 23 June 2022 05:28 AM UTC
  2. PowerBuilder
  3. # 2

You could reuse the existing repository, but I would see little benefit in doing so.  The native SVN interface stores the source code files different in the repository than PushOK does.  You likely have a folder for each PBL and the source code for each object in the PBL is stored in that subfolder.   You don't have to do that anymore with the native interface.  The native interface creates a ws_object directory and keeps all of the source under that folder.  You can move your existing PBLs into a common folder.

The end result is that you would end up with two sets of code in your repository.  I'd recommend creating a new one just to keep things cleaner.

Comment
There are no comments made yet.
Thorsten Kummer
Thorsten Kummer Accepted Answer Pending Moderation
  1. Friday, 24 June 2022 07:05 AM UTC
  2. PowerBuilder
  3. # 3

Dear all,

thanks for your answers, this helped me a lot.

Currently we are on SVN version 1.6.6 to be compatible with the PushOK bridge software which we'd like to get rid of.

The reason why we'd like to connect to our existing repositiory is that we'd like to keep the full object's history.

We plan to switch from PB 2019 R2 to PB 2021 (latest release). Unfortunately we do not have the time to wait for PB2022 GA.

As far as I know we would need to convert our repository structure to a newer on to be able to use it with PB 2021. We'll find out more soon during a migration prototype. We're talking about a PFC based application contained in more than 100 PBLs.

best regards

Thorsten

Comment
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.