1. Andrei Valentin Darie
  2. PowerBuilder
  3. Tuesday, 5 November 2019 13:22 PM UTC

Hi,

We are a group of 4 developers. We use GIT as source control but we have a lot of problems . The develop environment is not stable.

Several machine have the problem with Refresh function on Program Target and Workspace.

All the time shows "Failed to execute task" on Refresh function. We can not refresh data from Target and Workspace. We need to check on external programs example Git Extensions to see what PBL was modified and refresh one by one .

Somebody had bad experience with GIT / PowerBuilder integration?

When will APPEON create a good Integration between GIT and PowerBuilder?

Somebody know when Appeon will create easier ways to work with GIT and When GIT integration will accept branches ?

Regards,

Andrei

Tom Jiang @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 6 November 2019 02:54 AM UTC
  2. PowerBuilder
  3. # 1

Hi Andrei,

For the "Failed to execute task" issue, are you able to reproduce it every time? If you do know how to reproduce it, please open a support ticket and provide a reproducible test case at https://www.appeon.com/standardsupport/newbug

Regarding the working with branches, it will be supported in PB 2019 R2. The beta release is estimated to be early 2020. 

Regards,

Tom Jiang

Comment
  1. Andrei Valentin Darie
  2. Thursday, 7 November 2019 08:11 AM UTC


Hi,

I hope that the Git integration has been delevoped from scratch . I think the integration is weak. Maybe Appeon needs more focus on Git changes refresh from 3 three party manager as Git extension or similar. Found the changes and update the code when start the Powerbuilder Application. One weak point is when needs to share code with new developer trough GIT and add the GIT connection. NO way to works correctly. Some times works if the user modify the Windows Register...



Regards,



Andrei
  1. Helpful
There are no comments made yet.
Ramendra Singh Accepted Answer Pending Moderation
  1. Wednesday, 6 November 2019 04:07 AM UTC
  2. PowerBuilder
  3. # 2

Hi Andrei and Everyone

I also had difficult times working with GIT & PB 2017R3.

1. Never able to PUSH my changes through PowerBuilder always get the "Fat Forward" error 

2. Difficult to work with multiple branches at the same time as GIT don't recognize the PBL and consider them binary files. When I commit the changes and PUSH, I do it for PBLs as well and while merging the Feature Branch to Release or Master, I get the Conflicts which are very difficult to resolve as it's always the conflict in PBLs.

Is there a possibility to only commit the objects and not the container as we use to do it in TFS by maintaining a mapping file?

Thanks

Ramendra 

 

 

 

 

 

Comment
  1. Tom Jiang @Appeon
  2. Thursday, 7 November 2019 02:33 AM UTC
After the initial uploading of PBLs (when you add a workspace to the repository), PB is designed to NOT commit PBLs in all other operations (unless you explicitly do a Upload PBL or commit using a third party tool, which by default would also include changed PBLs). So if everyone understands and not commits PBLs, there shouldn't be any confilict on PBLs.



There was a bug where PB commits PBLs when a conflict happens with some objects, but it should have been fixed in the latest release. Please update to the latest version of 2017 R3 1880 or 2019 2082 if you are on an old version.

  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.