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

Resolved PowerBuilder 2017 R3 - Git (should .pbls be committed)

  1. Advice
0
Votes
Undo
  1. Steven Turner
    Steven Turner
  2. PowerBuilder
  3. Friday, 25 October 2019 14:21 PM UTC

Good morning,

Upon making a change to an object within a particular .pbl (acme1.pbl for example), I right-click on that .pbl (using TortoiseGit) to commit the change to that specific object. This commit is reflected in the ws_objects folder.

If I do a "git status" on my local repository, it will tell me that acme1.pbl is changed as well. Do we also need to commit the affected .pbl as well? If not, can I add "*.pbl" to my .gitignore file so that I won't be constantly asked to do something with the .pbl. This becomes an issue when trying to switch branches (if there are uncommitted changes).

Thanks in advance....
Steve

Themes and titlebars
application built using Powerbuilder 2019 database...
Accepted Answer
Matthew Balent
Matthew Balent Accepted Answer Pending Moderation
  1. Friday, 25 October 2019 15:53 PM UTC
  2. PowerBuilder
  3. # Permalink

Ideally you should set up your source folder separate from your 'application' folders (where the .PBLs reside), however in your situation you should get git to ignore the binary.  IMHO the only reason to put the .pbl files in source is when you have a 'gold release' (production code) and you want to have all the objects stored somewhere for posterity / future troubleshooting.

Comment
There are no comments made yet.
Responses (2)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 25 October 2019 20:27 PM UTC
  2. PowerBuilder
  3. # 1

I agree with Matt. When you have a release, put a copy of the PBL, PBD, and EXE files into source control. That way if you need to go back to an older version for some reason, all the files are there. Do that outside of the PowerBuilder GIT interface.

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Saturday, 26 October 2019 14:45 PM UTC
Just to be clear: It can be inside the Git interface, as long as it's just a copy of the pbl's in a separate folder of your source code.
  1. Helpful
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.