Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (5)

Resolved Issues With Large Git Repos

  1. Issue
0
Votes
Undo
  1. Richard Lynskey
    Richard Lynskey
  2. PowerBuilder
  3. Wednesday, 16 December 2020 15:41 PM UTC

We're wanting to migrate from Visual SourceSafe to git for our source control, but our repository size seems fairly large (51k files, 51 targets), and when we get to a certain size, PowerBuilder seems to fail under the load.

For example, every time I do a pull against my test git repository, with no more than a single change, I get "Failed to execute task." with no other information.

---------- Source Control
Git pull
Git client is pulling workspace. Please wait...
Importing m_genapp_frame.srm . . .
Compiling types for m_genapp_frame.srm . . .
Regenerating m_genapp_frame.srm . . .
Successful get of D:\app\app.pbl(m_genapp_frame.srm)
Failed to execute task.

Attempting to open the file in the sample above will throw up a weird error, but after restarting PowerBuilder, everything is fine.

Is anyone successfully working with larger repositories in git? Is this a workflow thing where I'm missing a step?

Alternate Characters in dynamic menu
Better profiling of opensheet
Responses (5)
Kevin Ridley
Kevin Ridley Accepted Answer Pending Moderation
  1. Saturday, 19 December 2020 16:13 PM UTC
  2. PowerBuilder
  3. # 1

I always thought the recommended GIT approach was 1 target per workspace and creating separate repositories, not have 1 repository for all targets?

Comment
There are no comments made yet.
Tobias Roth
Tobias Roth Accepted Answer Pending Moderation
  1. Friday, 18 December 2020 10:51 AM UTC
  2. PowerBuilder
  3. # 2

Hi Richard,

we have the same issue connecting to the git-workspace currently.

In the upcoming Release PB2019R3 there are a lot improvements, faster and more reliable refresh function and you can simply do a clone by TortoiseGit (with a manuel refresh inside the IDE).

 

We are using the following workaround until R3 is released:

1. Clone the repository with TortoiseGit.

2. Set the PB-Registry-Entries manually (Entries may differ slightly and need to be adjusted, especially the S identifier must be adapted) Easiest way is to copy the values of an existing git-workspace

 

Windows Registry Editor Version 5.00

[HKEY_USERS\S-1-5-21-3375370654-4084797731-1618270472-1207\SOFTWARE\Sybase\PowerBuilder\17.0\Workspace\D:$git$WORKSPACENAME$TARGETNAME.pbw\SourceControlVersion2]
"Type"="Git"
"Name"="GITUSERNAME"
"ServerURL"="https://git.xxxxxxxxx.de/xxxxxxxxxxxxx/xxxxxxxxx.git"
"LocalPath"="D:\\git\\WORKSPACENAME"
"Author"="AUTHOR NAME"
"email"="MAILADDRESS"
"LogAllActivity"=""
"LogFilePath"=""
"AppenOverWrite"=""
"Comments"=""
"RefreshRate"=""

 

Maybe this will help you in the meantime.

 

Regards Tobi

Comment
There are no comments made yet.
Tom Jiang @Appeon
Tom Jiang @Appeon Accepted Answer Pending Moderation
  1. Thursday, 17 December 2020 01:13 AM UTC
  2. PowerBuilder
  3. # 3

Hi Richard,

There is an issue refreshing a large project in the previous release, which is fixed in the coming PowerBuilder 2019 R3. Please try PowerBuilder 2019 R3 Beta release and see if it resolves your issue. 

You can download the beta release following this link: https://account.appeon.com/download

If you still see the issue in the beta release, please report a bug in our support portal: https://www.appeon.com/standardsupport/newbug

Regards,

Tom Jiang

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 16 December 2020 20:05 PM UTC
  2. PowerBuilder
  3. # 4

Hi Richard;

  There have been many GIT improvements to Appeon PB since its intial supported release of that SCC. What PB version & build are you using and also, what GIT software & version (and GIT Client) are you using?

Regards ... Chris

Comment
There are no comments made yet.
Govinda Lopez @Appeon
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 16 December 2020 18:29 PM UTC
  2. PowerBuilder
  3. # 5

Hi Richard,

 

Have you tried doing a "Refresh" of your Git files in PB, then perform the Git pull? You can try it directly from the popup menu from the System tree. Same menu where you perform the Git Pull.

 

 

Regards,

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.
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.