1. John Raghanti
  2. PowerBuilder
  3. Wednesday, 20 September 2023 19:41 PM UTC

Hi, stupid question. We're running PB 2022 Build 1900, and we're looking to migrate from VSS to Git using GitHub.

I am trying to set up a test repository, but I am not sure how to connect PB to GitHub. GitHub or Git isn't in my list of Source Control Systems.

Could anyone help me figure out how to get PB to recognize Git as a source control system?

Thanks!

John Raghanti Accepted Answer Pending Moderation
  1. Wednesday, 27 September 2023 11:31 AM UTC
  2. PowerBuilder
  3. # 1

Hi, we found the bug and reported it with our ticket. Wanted to close the loop here. In our ticket, Kitty He assured us in our ticket that: 

PB’s source control feature is not restricted by license type and all types of 
licenses have full access to the source control feature.

So we found that we could see the menu on our dedicated build machine. After discussing it in the ticket, we created a pristine virtual desktop and started from scratch. We couldn't see the menu even in that environment. We logged in as the build user and that had the same results. We started comparing INI files and config files, installed software to match the build machine and nothing worked. 

The person using the build machine does not regularly work in PB. All of our regular PB developers use the Library Painter. The Library Painter does not show the correct context menus. The guy on the build machine is using the System Tree. The Add to Source Control menu does show in the System Tree.

Comment
  1. Armeen Mazda @Appeon
  2. Wednesday, 27 September 2023 17:27 PM UTC
Once you upgrade to R2 you will have the source control functionalities also in the library painter. This is enhancement we did in R2: https://docs.appeon.com/pb/whats_new/ch01s01s16.html
  1. Helpful 1
There are no comments made yet.
kitty he @Appeon Accepted Answer Pending Moderation
  1. Friday, 22 September 2023 08:59 AM UTC
  2. PowerBuilder
  3. # 2

Hi John,

 

Can you not see any menus related to SVN & Git in your environment, including the menu Connect to Workspace?

We saw a similar issue with another customer before. It was caused by a third-party source code management software in the customer's environment. After uninstalling it, the various menus of source code management in PB become normal.

 

 

Regards,

Kitty

Comment
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Thursday, 21 September 2023 14:10 PM UTC
  2. PowerBuilder
  3. # 3

you're not on the latest version of 2022 (R2), but I don't think that the "standard" version of PB won't let you connect to source control.

(If so, then that's a bug in my opinion).

 

What if you close your workspace and then rmb click on "no workspace" ? (PB2019 R3):

When choosing "Connect to Workspace" you should see something like this:

regards

Comment
  1. Miguel Leeuwe
  2. Thursday, 21 September 2023 14:34 PM UTC
Well done! I don't think the 1900 build is their best version.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 22 September 2023 15:50 PM UTC
Hi Miguel;

It's not the build that is John's issue - it's the fact that he is using the very old (and deprecated) "Standard Edition".

Regards ... Chris
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Friday, 22 September 2023 17:34 PM UTC
John, what others said that Standard Edition cannot interface with Git/SVN is not true. Please look into Kitty's suggestion or open a support ticket: https://www.appeon.com/standardsupport/newbug
  1. Helpful
There are no comments made yet.
John Raghanti Accepted Answer Pending Moderation
  1. Thursday, 21 September 2023 11:08 AM UTC
  2. PowerBuilder
  3. # 4

Thanks Andreas for the detailed response!

I don't have "Add to Source Control" in my workspace menu? Any idea what I'm missing?

 

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 21 September 2023 20:03 PM UTC
Hi Andres;

Correct .. the "Standard Edition" does not support the new GIT / SVN options.

John would need to upgrade to the "Professional" edition.

Regards ... Chris
  1. Helpful 1
  1. Miguel Leeuwe
  2. Friday, 22 September 2023 08:40 AM UTC
That's crazy! Why would any of the powerbuilder versions for the so much praised shiny new Git source control not include it, just because being the "Standard edition" which conveniently you can no longer buy ?

Appeon should fix this.
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Wednesday, 27 September 2023 17:28 PM UTC
Chris is making mistake saying wrong thing. Standard Edition equally supports Git! It turns out problem was that they were trying to do source control in the library painter instead of system tree, which we have enhanced in R2 so if upgrading to R2 the source control will be also available in library painter: https://docs.appeon.com/pb/whats_new/ch01s01s16.html
  1. Helpful
There are no comments made yet.
Andreas Mykonios Accepted Answer Pending Moderation
  1. Thursday, 21 September 2023 06:57 AM UTC
  2. PowerBuilder
  3. # 5

Hi.

I guess you are trying to connect using properties of workspace.

But Git & SVN are not available in that window. To add an existing project to git, you have to right click on your workspace, then, in popup menu that appears you have to select "Add to Source Control" option.

A new popup will show on with two choices: Git and Subversion (SVN). Choose Git. You will be prompted for your name and an email (those should match with those on your git server). After submitting that information, a local repository of your project will be created (you can add a comment for first commit, but this is optional).

When you complete above steps, open again workspace properties. Go to source control tab. You should see the information for git in a screen like the following:

Here you will have to fill missing information:

  • User ID (for github in your case)
  • Password/Token (I believe that you will have to create a token in github)
  • Repository URL (you should create your repository in github, and put here it's url).

Also take a look at options available in advanced button (I suggest also to have TortoiseGit on your computer).

I strongly recommend you to read the following information from PB 2022 documentation:

Using Source Control - - Users Guide (appeon.com) and especially Using Git source control system - - Users Guide (appeon.com).

The documentation is good and the procedure is straight forward.

Andreas.

 

 

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.