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

Resolved How-to? GIT with PBLs in multiple directories

  1. How-to
0
Votes
Undo
  1. Roy Bungert
    Roy Bungert
  2. PowerBuilder
  3. Friday, 17 May 2019 08:12 AM UTC

Hello,

short question:

What is the best practice to configure GIT if you have your PBLs in more then one directory?

Situation:

We keep all PBLs from a project in its project directory. But there are some other common used PBLs (like the PFC), which are used in the project, in other directories. If I do any change in one of thes PBLs they are not under GIT.

Regards

 

Roy

pb 17 workspace size issue
Is there any solution on Powerbuilder continue int...
Responses (3)
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Tuesday, 21 May 2019 12:20 PM UTC
  2. PowerBuilder
  3. # 1

Hi Roy,

PB IDE git integration will NOT version control your PFC files because they live outside your PBW's root folder.

You need a separate PFC workspace and PFC target. That workspace allows PB IDE git integration to version control the PFC code.

HTH /Michael

Comment
There are no comments made yet.
Roy Bungert
Roy Bungert Accepted Answer Pending Moderation
  1. Tuesday, 21 May 2019 06:31 AM UTC
  2. PowerBuilder
  3. # 2

This means: It doesn't work ?

How other people resolve this problem?

Comment
There are no comments made yet.
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Saturday, 18 May 2019 12:26 PM UTC
  2. PowerBuilder
  3. # 3

Hi Roy,

I tried this out on PB 2017 R3 #1858. It boils down to PB IDE managing Git repo as a feature of your PBW workspace. Anything inside workspace root folder is maintained under source control by PB IDE. Same goes for any other source control system.

Anything outside the PBW's root folder remains outside automated source control by PB IDE. You need a separate PBW workspace to enable automated source control by the PB IDE.

I have experimented with complex Git repo configs. I learned that trying to coerce the IDE into more complex setups gives me more manual work outside the IDE.

My example:

  1. Current Git controlled workspace = C:\LearnPB\GitPilot\GitPilot.pbw
  2. Referenced code "outside Git" = C:\LearnPB\OutsideGit\SomewhereElse.pbl
  3. Workspace to manage "outside" code = C:\LearnPB\OutsideGit\OutsideFramework.pbw

HTH /Michael

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.