In fact, PB 2017 R3 is not yet mature regarding its integration with Git. Specially with TFS as mentionned in a webinar by Bruce Armstrong. 

I keep getting errors in the IDE when pushing to and pulling from remote repository.  

Errors like :

• Git client error code. Generic error...
• Reference was not fast-forwardable...
• Etc.

Doing the actions proposed by Julie won't help in my case.

Although, if you go outside the IDE, in your workspace folder and perform your operations through TortoiseGit or on the commandline (directly through Git local engine), it works fine.

Another example :

PBLs are not committed if you originally checked them (added to source control). Only text files (sra, srw, srd, etc.) are committed with IDE Git Commit. You need to do a manual IDE "Upload PBL" to commit the modified PBLs or do a "git commit -a" in the commandline to be able to push them later to the remote repo.

After the operations in TortoiseGit or commandline have been done, you can go back to PB IDE, perform a refresh on the workspace and your good to get back to work.

This is my workarounds for these errors in my case. 

If you find workarounds in the IDE, do not hesitate to share :-)

Is this issue get resolved in PB 2017 R3. Am still getting the same error using Appeon Powerbuilder 2017 R3. When you tried to push your code from IDE. Its show the below error

---------- Source Control
Git push
Starting to push workspace...
Git client is pushing workspace. Please wait...
Git client error code: Reference was not fast-forwardable.
Failed to push workspace.
Git push completed.
---------- Done Source Control

Hi Arthur, 

When you see the "Reference was not fast-forwardable" error, please first do a Pull, and then Push again.  

As for the last issue you pointed out, on OrcaScript, yes, it is confirmed to be a bug. We will fix in the next version.

Best regards,

Julie

Hello World

it's not an answer to the various git questions here, but an additional point to consider. We are using here a private github within a big company. This github instance doesn't allow authentication via username/password, instead a PuTTY key file (*.ppk) is required. Is there maybe already a possibility to set up PB2017R2 using a key file?

With the help of TourtoiseGit i was able to set it up so i can commit within PB, but Push to the remote repo obviously doesn't work. Would be nice if that's possible as well. Another point is, without having a valid username/password i can't change any source control properties (e.g. turn on logging).

cheers

martin

Hi Arthur;

    First of all ... Sorry for all your issues with the GIT SCC system. I am not a serious GIT SCC user - so I cannot add any value to your issue or questions. I mainly use SVN - in fact mainly VisualSVN personally.

   What I would like to suggest is that you open a Support Ticket for your specific GIT issue & questions and let someone from the Appeon Support Team who knows more about the GIT specifics respond.

Regards ... Chris