Shared PBL and Git
- How-to
- François Rossignol
- PowerBuilder
- Thursday, 14 May 2020 07:51 AM UTC
Hi,
I'm currently test the migration for some of our PB 12.5 apps to PB 2019 R2.
We started using Git for our latest app and want to use it for our older apps.
Here's the setup
I created a Git repo for each of the 3 apps.
Added to source control and published, so far so good.
But app1 shares a pbl with app2 and app3
app2 shares most of its pbl with app1 and app3
Each app has its own workspace.
Tha library list looks like
For App1
a1_p1.pbl
a1_p2.pbl
a1_p3.pbl
.....
..\app2\a2_p1.pbl
..\app2\a2_p2.pbl
..\app2\a2_p3.pbl
.....
For App2
a2_p1.pbl
a2_p2.pbl
a2_p3.pbl
.....
..\app1\a1_p1.pbl
For App3
a3_p1.pbl
a3_p2.pbl
a3_p3.pbl
.....
..\app1\a1_p1.pbl
..\app2\a2_p1.pbl
..\app2\a2_p2.pbl
..\app2\a2_p3.pbl
All the apps runs fine but my issue here is with Source Control
For exemple, I'm in the app3 workspace and modify a component in an app1 or app2 pbl
The corresponding "export" file in ws_object is not modified because as far as app3 is concerned the app1 and app2 pbl are not source controled.
Because the "export" file is not modified it cannot be commited in the correspondig repo ecause Git will assume the file is unchanged.
I know the simple solution would be to modify objets in a pbl when the relevant workspace.
But mistakes will happen and it can be a pain to go back and forth between workspace when you need to modify an app for the purpose on another.
Is there any workaround, or maybe another way to set this up ?
Thanks in adavance.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.