[ https://issues.jboss.org/browse/JBIDE-18911?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-18911 at 3/11/15 12:08 PM: -------------------------------------------------------------------- The bugzilla that's related to this jira issue was asking for 1 thing: # being able to use custom application template source code using an ssh url: {code} rhc app create kitchensink jbossas-7 mysql-5.5 -g small --from-code=git@github.com:openshift/kitchensink-example.git {code} # Additionally this jira tried also to allow ssh-urls for downloadable (standalone- and embeddable-) cartridges. 1) Seems implemented, the ssh-url is passed over to OpenShift as provided in the UI: !source-code.png! OpenShift then tries to clone the source from the given ssh-url. In OpenShift Online this then of course fails because we cannot give it the private key for the public key that we registered in github. !clone-error.png! If using OpenShift Enterprise we need to have this private key available on the broker host at /root/.ssh/ (see https://bugzilla.redhat.com/show_bug.cgi?id=1163964#c0) {quote} The reason why John could pass in comment 3, that is because he is using devenv, in the devenv instance, there is always ssh private key saved in /root/.ssh/, so when connecting to github via ssh protocol, node will use this private key to connect github by default, so git clone will always pass {quote} [~mlabuda] can you please organize a DEVENV where you have root access and can copy some private key to /root/.ssh/ and register the public key in github. 2) Is implemented for the UI validation only. OSJC wont accept the given ssh-url since it's not a valid URL and pass *null* over to OpenShift as shown above. was (Author: adietish): The bugzilla that's related to this jira issue was asking for 1 thing: # being able to use custom application template source code using an ssh url: {code} rhc app create kitchensink jbossas-7 mysql-5.5 -g small --from-code=git@github.com:openshift/kitchensink-example.git {code} The issue in jira tried also to: # allow ssh-urls for downloadable (standalone- and embeddable-) cartridges. 1) Seems implemented, the ssh-url is passed over to OpenShift as provided in the UI: !source-code.png! OpenShift then tries to clone the source from the given ssh-url. In OpenShift Online this then of course fails because we cannot give it the private key for the public key that we registered in github. !clone-error.png! If using OpenShift Enterprise we need to have this private key available on the broker host at /root/.ssh/ (see https://bugzilla.redhat.com/show_bug.cgi?id=1163964#c0) {quote} The reason why John could pass in comment 3, that is because he is using devenv, in the devenv instance, there is always ssh private key saved in /root/.ssh/, so when connecting to github via ssh protocol, node will use this private key to connect github by default, so git clone will always pass {quote} [~mlabuda] can you please organize a DEVENV where you have root access and can copy some private key to /root/.ssh/ and register the public key in github. 2) Is implemented for the UI validation only. OSJC wont accept the given ssh-url since it's not a valid URL and pass *null* over to OpenShift as shown above. -- This message was sent by Atlassian JIRA (v6.3.11#6341)