1. Arthur Hefti
  2. PowerBuilder
  3. Thursday, 26 July 2018

Hi

According to https://community.appeon.com/index.php/blogs/recent-blogs/enhanced-source-code-controlfor-pb2017-r2-r3 the pbg files will go away when using git and svn (what we currently do with PB2017 R2)

How should 3rd party build tools that make use of the pbg build a project from the source control? Do we need to create the pbg in the build process again?

Regards
Arthur

Chris Pollach Accepted Answer Pending Moderation
0
Votes
Undo

Hi Arthur;

   **  Update **

   PBG files are still required on all PB2017R3 applications.  The prerequisite for needing the PBG file is when executing ORCAScript in PB 2017 R3 as it contains the location of the ws_object  folder generated by GIT/SVN. This is where all object files will be located for SVN/Git to process.

   You can get around needing the PBG(s) by specifying the localprojpath property in you ORCAScript file. For example ...

scc set connect property localprojpath ‘c:\dev\pb2017\orderentry’

Note that the ws_object  folder must be located under that localprojpath  property declaration.

HTH

Regards ... Chris

 

 

Comment
There are no comments made yet.
  1. Thursday, 14 February 2019
  2. PowerBuilder
  3. # 1
David Vasconcelos Accepted Answer Pending Moderation
0
Votes
Undo

Coming to the Party a bit late on this.  My understating is that PBG files went away in PB2017 R3 regardless of what version control system you were using.  After reading this I am now a bit confused.  We can't upgrade to R3 because we are using an older Source Control called RCS which needs PBG... So the question is to confirm my original understanding.  Did PBG files go away, so for me to upgrade to R3 I would need to replace RCS is this True?

Thanks

Dave V.

Comment
Hi Dave;

No, PBG files are still used when you are connecting to a SCM using the long time standard SCCAPI feature from the "WorkSpace" level.

Its only If you use the new *native* SVN or Git SCM connection feature - then PBG files are not used.

HTH

Regards ... Chris
  1. Chris Pollach
  2. Monday, 11 February 2019
Thanks for the clarification Chris, that is good news..that means if the client wants to go to R3 our current source controls system which is old (RCS) will still work...
  1. David Vasconcelos
  2. Tuesday, 12 February 2019
Yes, they should work the same SCCAPI wise in PB2017Rx. ;-)
  1. Chris Pollach
  2. Tuesday, 12 February 2019
There are no comments made yet.
  1. Monday, 11 February 2019
  2. PowerBuilder
  3. # 2
Ken Guo Accepted Answer Pending Moderation
0
Votes
Undo

Hi Arthur,

Yeah, it won’t generate any PBG file when using GIT/SVN SCC in PB 2017 R3 and PB 2019. Instead it uses the ws_objects folder. If you need the Object List Files, you can create it with the files in the ws_objects folder, i.e. if it is required to use a PBG in a third party software, you can utilize the ws_objects folder to create it on your own.

If you use PowerGen tool, it supports 2017 R3 and 2019.

 

Regards,

Ken

Comment
There are no comments made yet.
  1. Wednesday, 23 January 2019
  2. PowerBuilder
  3. # 3
Phil Wallingford Accepted Answer Pending Moderation
1
Votes
Undo

Hi Armeen, et. al.

A little background to PowerGen's use of PBGs...

We (E. Crane) introduced Object List Files (OLFs) before PBGs came out.  Because we needed a way to map object files to PBLs (what PBGs do) for our Bootstrap Import function.  Our Bootstrap Import was released a couple years before anything else like it existed.  (Yes we should have trademarked the term/process!)

From the beginning OLFs could either enumerate the objects or use wild cards in directory to map all the files in a directory to a particular PBL.

When PBGs were introduced, we supported them immediately in addition to keeping support for OLFs.

In fact we introduced functions to produce PBGs based on an existing set of PBLs.  We did this from demand from our customers who were finding the PBG files maintained by PowerBuilder would often get out sync with the application.

We have maintained support for all of this through all versions of PowerBuilder 2017 (and the new PowerBuilder 2019 Beta).  And have provided support specifically for the new source directory structure for the Git/SVN integration.

So PowerGen users with Git/SVN integration can either maintain PBG files for use with existing build scripts or use OLFs.

Regards,

Phil

 

 

Comment
There are no comments made yet.
  1. Monday, 21 January 2019
  2. PowerBuilder
  3. # 4
Stuart Macandrew Accepted Answer Pending Moderation
0
Votes
Undo

Sorry - I take that back - the above comment is inaccurate. The PBG file IS still maintained under the SCCS interface and PB2017R3 works exactly the same as PB2017R2. I had not examined the commit messages carefully enough to see the PBG file still being maintained when I responded above.

Comment
There are no comments made yet.
  1. Tuesday, 7 August 2018
  2. PowerBuilder
  3. # 5
Stuart Macandrew Accepted Answer Pending Moderation
0
Votes
Undo

No - it appears the PBG file has gone away for the SCCS interface as well.

We are running PBSCC-Proxy and TortoiseSVN, to a SVN repository. From a Powerbuilder perspective the source-controls interface is SCCS.

Under PB2017R3 when I add an item to source control from the PB IDE the PBG file is not maintained.

Which will mean there is no way that other users - including our build workstation using ORCA - will import that new source item to their PBL.

I have not got my head around how much work there is for us to reconfigure for us to use the PB2017R3 SVN interface. And given our existing configuration has worked well I am reluctant to do that.

Comment
There are no comments made yet.
  1. Tuesday, 7 August 2018
  2. PowerBuilder
  3. # 6
Bruce Armstrong Accepted Answer Pending Moderation
0
Votes
Undo

Which 3rd party tool did you have in mind?

PowerGen from ECrane has an option to use OFL (object file lists) to match the source code to the PBLs.  With the latest release they added the option to create OFLs based on the ws_objects folder structure.  So you run that, and then you'll have the OFLs you need to do the build.

Comment
There are no comments made yet.
  1. Friday, 27 July 2018
  2. PowerBuilder
  3. # 7
Armeen Mazda Accepted Answer Pending Moderation
0
Votes
Undo

The short answer is the third-party tools would need to modify so they are no longer relying on the PBG since that is not generated.  To the best of my knowledge I think PowerGen is the only popular third-party build tool that has relied on the PBG.  My understanding is that they are committed to adapting PowerGen to be compatible with newer versions of PowerBuilder, so it's possible there is a newer version of PowerGen that is compatible or there would be one soon.  I would recommend contacting the third-party vendor.

Comment
If I read it correctly, the PBG file going away is only for GIT & SVN. Is that true?
  1. Roland Smith
  2. Friday, 27 July 2018
Yes, but still generated if you use the MSSCCI interface (for backwards compatibility reasons). So only if switching away from the MSSCCI interface to the new native Git/SVN interfaces AND the 3rd party tools you use cannot function without PBGs then you may need to do some workaround yourself or ask the 3rd party vendor to update their solution to be fully compatible with how PB 2017 and newer operates.
  1. Armeen Mazda
  2. Wednesday, 23 January 2019
For those using PowerGen and PowerBuilder 2017 R3 (and later) and Git/SVN integration, we have released to Beta (February 2019) V10.1 which lets you Bootstrap Import™, Synchronize and Compare your application directly from the Git/SVN directories.



We have maintained the ability to use these functions with Object List Files (our precursor to PBGs) and PBGs for backwards compatibility with existing build processes.
  1. Phil Wallingford
  2. Monday, 11 February 2019
There are no comments made yet.
  1. Thursday, 26 July 2018
  2. PowerBuilder
  3. # 8
  • Page :
  • 1


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