• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Connect to Workspace dialog is not allowing connection to GitHub

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
You need to be logged in to view a user's profile.
View Replies (5)

Resolved Connect to Workspace dialog is not allowing connection to GitHub

  1. Advice
0
Votes
Undo
  1. Kyle Griffis
    Kyle Griffis
  2. PowerBuilder
  3. Wednesday, 19 August 2020 23:12 PM UTC

Hi All,

We have been installing and setting up GitHub repositories for our development team and have run into a situation that is stopping us from allowing developers to switch from a network repository to a GitHub server repository. frown

Here is what is happening, when we use the connect to workspace option, the dialog is repopulating the Repository URL to the network drive repository and it's Workspace.  When we clear out the values and paste in the URL to the GitHub repository it fails to connect.  However we can connect to the repository in SourceTree so we know the URL and other pertinent information is valid.

We have searched the Help files and done an exhaustive search for answers on line without finding a resolution. 

Questions and concerns are many - How do you clear out the values from the dialog?  Where are these values stored?  Does this mean we have to modify the registry? 

These are the questions that we have and would like some direction as to what we can do.  If we can not change from one repository to another thru the PowerBuilder IDE due to having number of applications (20+), this is really a show stopper.  Surely there is a method for clearing out the Source Control connection, how in the world do you do this, please do not tell me that I have to modify registries, that's not an practical answer or a best practice protocol. sealed

Thank you for your time.

Kyle

Here's a snippet of the dialog

 

 

PowerClient (in pb 2019 r3)
PostgreSQL: "Select Data Source" pops up with eve...
Responses (5)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 20 August 2020 14:46 PM UTC
  2. PowerBuilder
  3. # 1

Hi Kyle;

  Are you using the latest PB 2019 R2 IDE as there has been many SCM fixes since PB 2017?

Regards ... Chris

Comment
There are no comments made yet.
Kyle Griffis
Kyle Griffis Accepted Answer Pending Moderation
  1. Thursday, 20 August 2020 14:59 PM UTC
  2. PowerBuilder
  3. # 2

Chris,

We are on 2017 R3 Build 1858, haven't migrated up to 2019 yet.  Are you saying that the SCM fixes are only in 2019?

Thank you Chris, for your reply!

 

Kyle

 

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 20 August 2020 15:18 PM UTC
Hi Kyle ... there were a few SCM related fixes in the last Maintenance Release (build 1915).

FYI: https://file.appeon.com/download/APB/2017/R3/MR/build_1915.00/PowerBuilder%202017R3_1915_to_2017R3_1880_fixes.htm

This particular problem though does not resonate with me currently.
  1. Helpful
There are no comments made yet.
Kyle Griffis
Kyle Griffis Accepted Answer Pending Moderation
  1. Thursday, 20 August 2020 15:46 PM UTC
  2. PowerBuilder
  3. # 3

Chris,

 

Is there a document that describes the enhancements to the SCM for 2019?  It sounds like the thing to do is look into migrating the developers and applications but before I can take on that task I need to know more of what that offers.

 

Thanks!

 

Kyle

Comment
Load more comments
Kyle Griffis
  1. Kyle Griffis
  2. Thursday, 20 August 2020 16:26 PM UTC
Perfect, thank you!
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 20 August 2020 16:29 PM UTC
Welcome! Also, drill down from those above links to the "Bug Fixes" section in each release to see the various SCM related fixes.
  1. Helpful
Kyle Griffis
  1. Kyle Griffis
  2. Thursday, 20 August 2020 16:35 PM UTC
Will do.
  1. Helpful
There are no comments made yet.
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Friday, 21 August 2020 06:45 AM UTC
  2. PowerBuilder
  3. # 4

Hi Kyle，

When you open Connect to Workspace, it will display the last Git info by default. It is mainly for the user to connect to the recent Git program quickly.

This info is saved into the following registry:

Computer\HKEY_CURRENT_USER\Software\Sybase\PowerBuilder\17.0\Workspace\Git

This Git info in the registry is only used to fill the default value and won’t affect the Git connection in Connect to Workspace.

In the screenshot you provided, I saw that you entered ‘F:\APPS\PowerBuilder\2017\GitPOC’ in the Repository URL.

Generally speaking, it should be an URL with https, for example, https://github.com/testuser/test.

Can Git connect successfully if you enter a valid URL?

 

If you still fail to connect to GIT, I suggest you open a ticket in the Appeon support ticketing system (https://www.appeon.com/standardsupport/newbug).    

Additionally, I also suggest you upgrade PB to the latest PB 2017 R3 Build 1915 version to try because some bugs will be fixed in a higher version.

 

Regards,

Ken

Comment
Kyle Griffis
  1. Kyle Griffis
  2. Friday, 21 August 2020 12:40 PM UTC
Very much appreciated Ken, Thank you!



Kyle
  1. Helpful
There are no comments made yet.
Kyle Griffis
Kyle Griffis Accepted Answer Pending Moderation
  1. Friday, 21 August 2020 12:40 PM UTC
  2. PowerBuilder
  3. # 5

Thank you Ken and everyone else who has help with this issue.

laughing

It has been a real pleasure to work with you and have some solid advice!

 

Kyle

 

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.