1. Raymond Longoria
  2. PowerBuilder
  3. Friday, 19 November 2021 22:15 PM UTC

We are in the process of getting our Powerbuilder code (2019 R3) into git. It is a suite of applications and each one has its own workspace.  All of the applications access a common pbl that is in a separate folder. When I created the local repository for a workspace, it did not include the shared pbl. Any suggestions on how to create a local repository for a shared pbl?

kitty he @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 31 May 2023 07:59 AM UTC
  2. PowerBuilder
  3. # 1

Hi Raymond,

 

The principle of PB's Git is the same as that of Tortoise Git. If you want to use Git to manage an entire application, all objects must be included in a parent directory (including objects to be used for sharing), otherwise objects not included in the application directory cannot be uploaded.

 

If multiple applications use a set of common shared objects, there are two options:

  1. Multiple applications and shared objects are placed in the same repository (you only need to maintain a single copy of shared objects).
  2. Each application has its own repository, and a copy of shared objects is stored in each repository (disadvantage: it is inconvenient to maintain the shared objects).

 

Regards,

Kitty

Comment
There are no comments made yet.
Jay Hastings Accepted Answer Pending Moderation
  1. Tuesday, 30 May 2023 17:08 PM UTC
  2. PowerBuilder
  3. # 2

I have this same issue.  Moving my PN2019R3 pbls to GIT and wondering how my Workspaces should be organized as it seems GIT will take every PBL in the specified directory.  I have multiple apps in multiple directories with some PBLs shared across apps.  I have objects with the same names in multiple apps within one directory.  I'm not sure how to set this up to avoid collisions.

 

Thanks in advance

 

Jay

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