Red Hat Bugzilla – Bug 1299619
Business Central Repo Clone Fails To Clone SCP Style SSH URLs
Last modified: 2016-03-17 09:00:28 EDT
Created attachment 1115946 [details]
Error screen shot
Description of problem:
Git supports two styles of URI's for SSH protocol. Business Central fails with "invalid URL format" when using the SCP style for SSH. This problematic because github by default uses the SCP style for SSH and does not seem to support the SSH style URL anymore.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1) Go to the admin tab
2) Click repositories->Clone Repository
3) Fill out the form using any ssh URL protocol provided by the github UI. I used firstname.lastname@example.org:sherl0cks/TestKnowledgeRepo.git
See screenshot. Error with "invalid URL format"
It clones the repo just like https URLs.
Created attachment 1123137 [details]
This is a screenshot showing that business central aligns with the Github recommended standard.
Has there been a JIRA created for this. Do we have any what the target fix version is?
RE: GitHub recommendation
The goal here is to use oncommit githooks to sync with a remote git repo. If customers can accomplish this using an alternative approach, I am OK. That said, we have a few issues:
1) Many customers just use SSH, and most SSH providers for git (including GitHub & GitLab) use the scp style protocol. What github recommends and what customers actually do don't always align.
2) The current implementation of githooks from jGit does not provide a way (that I can find today) to have jGit perform the actual git operations. Instead, jGit delegates to the OS to execute the hook which in turn requires git on the OS to perform the operation. This means if you want to use an oncommit githook to push to a remote a repo, then you need to use ssh or some custom way of storing the username/password, as the username/password in jGit is not available.
@Mike - 6.2 patch 2, which is early/mid March. You can tell because this issue blocks https://bugzilla.redhat.com/show_bug.cgi?id=1299870 which has the appropriate flag
Keys without passphrase can be supported by relaxing the url validation and should work.
Verified with BPMS 6.3.0.ER1.