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

Resolved PBG's and R3 issue

  1. Issue
0
Votes
Undo
  1. David Watson
    David Watson
  2. PowerBuilder
  3. Tuesday, 15 October 2019 16:59 PM UTC

We are currently using Git integration in PB 2017 R2 and moving to R3.

Like others, we've set it up with .gitignore leaving out PBL's.  However, in PB 2019 R3 we have an anomaly where new objects that are "added" to a pibble show up in the ws_objects folder but do not show up in the IDE under the pibble.  This leads to inability to run in IDE and also deployed/built code seems not to be working.

In R2 when one person added some objects and our Git/TFS shows changes to the .pbg.  Those developers new objects are in the pbl's as they're supposed to be.  An R3 developer added objects and source control DOES NOT show changes to the .pbg and his are not showing up.

I assume this is an issue of the .pbg's not being "part" of R3.

 

With the elimination of .pbg's in R3 how do we properly add objects to pibbles so that they show in the IDE?

Parsing JSON numbers and decimal point character
Problems using Orca Script for get Latest
Responses (4)
Tom Jiang @Appeon
Tom Jiang @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 16 October 2019 08:41 AM UTC
  2. PowerBuilder
  3. # 1

Hi David,

2017 R3 imports all the objects in a pbl.src folder into the corresponding PBL, while 2017 R2 only imports the ones listed in the pbg file. They both work fine if all of your developers were using the same version (R2/R3). So the simple solution is to have all of your developers upgrade to 2017 R3, so no one will need the pbg file anymore.

BTW, the reason to get rid of pbg files is to avoid unnecessary merge conflicts that happen when different people add differnt objects in the same PBL. So it is in your benefit to upgrade to 2017 R3 from this perspective.  

Regards,

Tom Jiang

Comment
There are no comments made yet.
Arthur Hefti
Arthur Hefti Accepted Answer Pending Moderation
  1. Wednesday, 16 October 2019 03:56 AM UTC
  2. PowerBuilder
  3. # 2

Hi

  1. Developer 1 creates the new object. This shows up with a plus sign in the system tree. Click right on the object in the system tree and choose "Git Commit". The do a "Git Push" on the workspace.
  2. Developer 2 does a "Git Pull" on the workspace and then a "Refresh" (all right mouse button).

- In PB Workspace: Git Commit does not only commit but also add a new object
- Commit can be done on the whole workspace or on single object or libraries
- Refresh can be done on the whole workspace or on single objects or libraries

Of course you can use the git command line or Tortoise Git GUI as well for these actions (except refresh)

PBGs are obsolete. 

Regards
Arthur

Comment
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Tuesday, 15 October 2019 19:59 PM UTC
  2. PowerBuilder
  3. # 3

The GIT & SVN interface doesn't use .PBG files. I'm not an expert on this feature but I believe you are supposed to do a Pull from the workspace menu and it will download from the server to your local repository and then import new/changed objects into the library.

 

Comment
There are no comments made yet.
David Watson
David Watson Accepted Answer Pending Moderation
  1. Tuesday, 15 October 2019 19:40 PM UTC
  2. PowerBuilder
  3. # 4

I managed to repair by (from R2) manually importing the missing objects into the PBL's which causes an update to the .pbg's, the source files and it looks like either hidden files or directories.  Still don't understand how it is supposed to work in R3 when adding objects.

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.