1. Jostein Ullestad
  2. PowerBuilder
  3. Monday, 11 May 2020 08:00 AM UTC

Hi Expert.

We have successfully been using PowerBuilder 2019 Build 2082 with Git for some time. We are using Azure DevOps to host our repos. It was decided to move the repo to another location on Azure, and then issue occurred for one developer. We followed the steps indicated in documentation https://docs.appeon.com/appeon_online_help/pb2019r2/pbug/ch03s03.html#git_get

We selected from PowerBuilder "connect to workspace". All source files get downloaded including the PBL files.

After this successful operation, we perform "Refresh" in order to update the PBL files with the latest sr? files. The PBL files in Repo are not kept up to date. This is also successful.

 

We modify an object within PowerBuilder and see the green checkmark come on in the tree view. When I revert the changes in PowerBuilder painter the green checkmark goes away. Just as expected.

Leaving the changes intact and with green checkmark visible (also the file in the containing folder is marked as modified with the red and white exclamation badge), right-click the object and in the popup menu choose "Git revert", here is the issue. The dialogue presented does not include the folder structure or the modified file. Is it simply only showing the local git repository root folder. If we try to git commit from PowerBuilder, the same thing happens, the dialogue is not listing the file modified.

Doing revert action from the containing folder using TortoiseGit, that dialogue shows the sr? file as expected.

Another developer performing the same task has the dialogue showing details as expected.

Reverting back to the previous workspace and modifying an object, the revert and commit dialog is lising the object as expected.

 

I am a bit lost for ideas now and have not found a solution for this issue, any help would be much appreciated - thank you.

 

PowerBuilder 2019 Build 2082

TortoiseGit 2.10.0.2

git 2.25.1.windows.1

Windows 10 Pro 1903, 64 bit

Attachments (2)
Jostein Ullestad Accepted Answer Pending Moderation
  1. Wednesday, 13 May 2020 11:35 AM UTC
  2. PowerBuilder
  3. # 1

Here is what was done to overcome this issue:

  1. Created "Alternate Credentials" in Azure DevOps. Not thrilled about that as beginning March 2nd 2020, Azure DevOps will no longer support Alternate Credentials authentication.
  2. Updated PowerBuilder to 2019 R2 Build 2328.
  3. Then removed the local copy of the repository within File Explorer.
  4. Started PowerBuilder after a reboot and selected "Connect to workspace"
  5. Got the latest files from the repository.
  6. "Refresh" from the system tree view.
  7. Full build.

 

Comment
  1. Armeen Mazda @Appeon
  2. Wednesday, 13 May 2020 15:52 PM UTC
Thanks for sharing the solution!
  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.