1. Fredrik Fahlén
  2. PowerBuilder
  3. Friday, 24 January 2020 13:53 PM UTC

Hello,

My company is using Bitbucket for source control. This worked fine with PowerBuilder 2017 R2. Commits, pushes and pulls were all OK.

In PB 2017 R3 and PB 2019 there are some problems when using Bitbucket (Git) as source control. When doing a Commit in PB I get prompted to preview changes and add a comment (as expected). After the commit everything looks ok in the status output window as follows:

---------- Source Control
Git commit
Git client is finding files. Please wait...
Git client has finished finding files. 1 file(s) found.
Git client is committing files. Please wait...
Git commit success.
Git commit completed.
---------- Done Source Control

The file(s) is not committed in PowerBuilder and in Sourcetree the file is not staged/committed, but for some reason my commit-comment is visible in Sourcetree. 

When doing a Push from PowerBuilder I get the following in the status output window:

---------- Source Control
Git push
Starting to push workspace...
Git client is pushing workspace. Please wait...
Pushing current objects: 0, total objects: 2.
Pushing current objects: 2, total objects: 2.
Push workspace success.
Git push completed.
---------- Done Source Control

After this operation nothing is pushed and the file is still marked as changed in PowerBuilder. To be sure nothing was messed upp with my repository, i created a new repository and added my PB workspace from PowerBuilder using the menu "Add to Source Control...", which worked fine.

Doing Commit, Push and Pull from Sourcetree works fine as well.

All this worked fine without any problems in PowerBuilder 2017R2. 

Anyone that can help us? It's really annoying not to be able to "check in" directly in PowerBuilder. 

/Fredrik

 

 

 

 

Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 24 January 2020 14:04 PM UTC
  2. PowerBuilder
  3. # 1

Please open a support ticket:https://www.appeon.com/standardsupport/newbug

Comment
There are no comments made yet.
Michael Kramer Accepted Answer Pending Moderation
  1. Friday, 24 January 2020 14:07 PM UTC
  2. PowerBuilder
  3. # 2

Sounds strange - and wrong, I agree.
What is the filetype of the troublesome file(s)?

NOTE: Anyone else using PB 2019 (or PB 2017 R3) with BitBucket successfully? => Please join!

I don't have BitBucket. I do use SourceTree.

/Michael

Comment
  1. Michael Kramer
  2. Friday, 24 January 2020 15:53 PM UTC
As Armeen suggests: Open support ticket - unless a solution appears here within a few hours (or by Monday morning).

Lycka till, /Michael
  1. Helpful
  1. Fredrik Fahlén
  2. Friday, 24 January 2020 17:26 PM UTC
Hello :-) Ticket is opened and Mr Chris Pollach is going to look into this!
  1. Helpful
  1. Michael Kramer
  2. Friday, 24 January 2020 17:35 PM UTC
Great! Enjoy your weekend.
  1. Helpful
There are no comments made yet.
Vipul Prakash Srivastava Accepted Answer Pending Moderation
  1. Tuesday, 14 December 2021 07:18 AM UTC
  2. PowerBuilder
  3. # 3

Hi Fredrik,

Greeting for the day.

Small help required from your side, as you have mentioned GIT PUSH/GIT PULL/Commit all are working fine with Appeon Power Builder 2017 R2 Version .

But I am Facing some issue with GITPUSH/GITPULL with Appeon PowerBuilder2017 R2.

Below is the issue:

My company is using BitBucket Code repository with Power Builder 2017 R2 version.

I can commit the code from Power Builder 2017R2 but when I am going to push the changes it is throwing below error:

Git client is finding files. Please wait...
Git client has finished finding files. 1 file(s) found.
Git client is committing files. Please wait...
Committing file: Source/WRK/ABC.PBL.
Git commit success.
Upload PBL
Git push
Starting to push workspace...
Git client is pushing workspace. Please wait...
Git client error: Generic error..
Failed to push workspace.
Git push

GitPush is working fine from GITBASH command prompt.

Could you please help me on that part.

 Regards

Vipul

 

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.