1. Steven Turner
  2. PowerBuilder
  3. Tuesday, 29 December 2020 16:13 PM UTC

Good morning,

We are using 2017 R3 with Git as source control. After making changes to existing objects and committing the object to Git, the object (sometimes) doesn't display in Appeon upon a Pull from the repository. We are forced to do a "Refresh" on the Target for the object to eventually show the latest change. This doesn't happen each time. What is causing this anomaly?

Thanks in advance....

Steve Turner

Accepted Answer
Drew Buchanan Accepted Answer Pending Moderation
  1. Thursday, 31 December 2020 19:39 PM UTC
  2. PowerBuilder
  3. # Permalink
1
Votes
Undo

Are you performing the Git actions inside of PowerBuilder or using an external Git client?

PowerBuilder's dev environment works on pbls, but Source Control works on the ws_objects folder. When you make a change in a pbl, PowerBuilder exports the object to the ws_objects folder and that gets source controlled, but PowerBuilder doesn't execute that code. If you make changes to the object outside of PowerBuilder, for instance pulling with SourceTree, then that change won't be in the pbl and visible to the PowerBuilder development environment until you Refresh. Refresh in PowerBuilder rebuilds all pbls from the contents of their respective ws_objects folder, which may explain this issue.

Comment
There are no comments made yet.
Steven Turner Accepted Answer Pending Moderation
  1. Thursday, 31 December 2020 19:51 PM UTC
  2. PowerBuilder
  3. # 1
0
Votes
Undo

Steps to recreate:

1) Connect to workspace via 2017 R3 (connect as Git)
2) All items are eventually pulled down.

3) Open 2017 R3 and verify that items that were just previously committed are missing
4) Do a refresh on the Target and/or Workspace
5) Missing items are then Imported into the corresponding PBLs

*** All Refreshing is done within 2017 R3 ****

TortoiseGit is used to commit items to the repository

Thanks...

 

Comment
When you pull the workspace for the first time, the pbls are sent in the state they were most recently committed. Unless you're committing pbls at every commit, the pbls will be missing some changes. The refresh synchronizes your pbls with the ws_objects folder.



Say that changes were made at C2, C3, and C4, but pbls were only committed at C2. Pulling the workspace down will result in PowerBuilder seeing the pbls in the state they were in at C2. Refreshing takes the changes from C3 and C4 and imports them into the pbl.

C4 - 0800

C3 - 0700

C2 - 0600 <- pbls committed here
  1. Drew Buchanan
  2. Thursday, 31 December 2020 20:04 PM UTC
When you connect to the workspace for the first time If you are not sure whether the PBL files on the source control server is the latest or not, it is recommended you do a Refresh manually. In other words, unlike the "Git Pull" command, the "Connect to Workspace" doesn't automatically trigger the refresh. The coming PowerBuilder 2019 R3 has an option to automatically trigger the refresh after "Connect to Workspace".
  1. Tom Jiang @Appeon
  2. Monday, 4 January 2021 01:14 AM UTC
Adding to what Tom said, there are tons of enhancements for Git in PB 2019 R3, and this version is also a long-term support (LTS) version just like PB 2017 R3. It is scheduled to release end of this month. I recommend upgrading.

https://docs.appeon.com/pb2019r3/whats_new/Source_control_enhancements.html
  1. Armeen Mazda @Appeon
  2. Monday, 4 January 2021 01:19 AM UTC
There are no comments made yet.
Tom Jiang @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 30 December 2020 05:07 AM UTC
  2. PowerBuilder
  3. # 2
0
Votes
Undo

Hi Steve,

The pull action always triggers an automatic refresh. Is it possible that you got an error during the automatic refresh? Please check the output window and see if there is any error message. 

On the other hand, I suggest that you try PowerBuilder 2019 R3 Beta (https://account.appeon.com/download), it support creating and switching branches and it always shows the error message on a separate window. The GA release will be available soon.

Regards,

Tom Jiang

Comment
There are no error messages displayed.

*** Side Note ***

We are also putting the .PBLs in the repository (not my decision). Could committing the .PBLs be the cause?
  1. Steven Turner
  2. Thursday, 31 December 2020 11:40 AM UTC
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.