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

Resolved Git push PBL's

  1. How-to
0
Votes
Undo
  1. Bjarne Anker
    Bjarne Anker
  2. PowerBuilder
  3. Wednesday, 15 May 2019 06:07 AM UTC

Hi.

 

Is there an option i PB2017 to always push PBL's to Git?

It looks like we have to right click and choose "Upload PBL" now to also push the PBL's in addition to the .sr* files?

 

This could be a nice addition to have double backup of the source.

 

Regards,

 

Bjarne Anker

Maritech Systems AS

Norway

How to enter ALT key codes (unicodes) for symbols
PB12 and PB2017 Applications installed in same mac...
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 15 May 2019 15:15 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Bjarne;

   It's the same in SVN as well ... the PBL's are no longer automatically uploaded to the SCM in the later PB2017Rx release and you now have to upload each PBL via the "Upload PBL" RHMB option.

  My suggestion is what I always do with any SCM over the past 30+ PB years ... when you first register your PB App or you release a new version ... ZIP up all the PBLs and then use the SCM client to upload the ZIP file. That way, you always have an easy set-up for a new PB developer and a handy way to perform regression testing from a "known" state.

Just my $0.02.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Responses (2)
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Saturday, 18 May 2019 14:04 PM UTC
  2. PowerBuilder
  3. # 1

Hi Bjarne,

As you point out, the PBL file is a "duplicate" of the source code in *.SR? files.

You can adjust your .gitignore file to exclude .PBL files. That's one approach. You often see .gitignore excluding .EXE, .DLL, etc.

Alternative (my approach currently) is to manually commit updated .PBL files just before pushing changes in my local git repo to next level of git repo. My setup:

  • Central repo - where we do branching/merging
  • PC local repo - my local "master" managing the hand-offs between local repos and central repos.
    My PB specific and SQL specific repos all sync back to this PC local repo.
  • PB specific repo - one for each combo of PBW workspace and branch.
  • SQL specific repo - one for each combo of MS SQL Server Mgmt. Studio solution and branch - the DB equivalent of my PB workspaces.

This works for me. You may decide to manage your git repos in a completely different structure.

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.