This question is locked. New answers and comments are not allowed.
myTeamWorks
Top achievements
Rank 1
Rank 1
myTeamWorks
asked on 26 Feb 2013, 01:57 PM
Hello,
After trying to clone the project from our GIT server, I started receiving this message on Icenium Graphite.
Using the GIT bash, I can clone the project with no problems, but I cannot do it from Icenium.
Thanks in advance for your help,
Carlos
After trying to clone the project from our GIT server, I started receiving this message on Icenium Graphite.
Using the GIT bash, I can clone the project with no problems, but I cannot do it from Icenium.
Thanks in advance for your help,
Carlos
3 Answers, 1 is accepted
0
Ilian
Top achievements
Rank 1
Rank 1
answered on 28 Feb 2013, 05:47 PM
Hello Carlos,
Thank you for using Icenium. I am afraid that we can not reproduce this issue with the information you have provided. Could you please provide more info what Git server are you using and if it is public so Icenium's server can access it?
Greetings,
Ilian Iliev
the Telerik team
Thank you for using Icenium. I am afraid that we can not reproduce this issue with the information you have provided. Could you please provide more info what Git server are you using and if it is public so Icenium's server can access it?
Greetings,
Ilian Iliev
the Telerik team
0
myTeamWorks
Top achievements
Rank 1
Rank 1
answered on 01 Mar 2013, 08:16 AM
Hello Ilian,
Thanks for your answer.
The repository we were using was on out git server (public address). It has been used by the team (using Icenium) before, but when I needed to clone it I received the error from Icenium. I asked my colleagues to try to clone it themselves into another Icenium Project, but everyone had the same issue.
As I was able to clone it using the GIT Bash, I pushed it into a new BitBucket Repo. Cloning the it from BitBucket (with Icenium) worked for me, but some of the team members were getting a "An existing connection was forcibly closed by the remote host" error when cloning it from Icenium. Using Git Bash it works always.
I'd say that it's something related to the GIT implementation on Icenium's client.
The project is not huge, some dozens of files.
Thanks,
Carlos
Thanks for your answer.
The repository we were using was on out git server (public address). It has been used by the team (using Icenium) before, but when I needed to clone it I received the error from Icenium. I asked my colleagues to try to clone it themselves into another Icenium Project, but everyone had the same issue.
As I was able to clone it using the GIT Bash, I pushed it into a new BitBucket Repo. Cloning the it from BitBucket (with Icenium) worked for me, but some of the team members were getting a "An existing connection was forcibly closed by the remote host" error when cloning it from Icenium. Using Git Bash it works always.
I'd say that it's something related to the GIT implementation on Icenium's client.
The project is not huge, some dozens of files.
Thanks,
Carlos
0
Ilian
Top achievements
Rank 1
Rank 1
answered on 06 Mar 2013, 03:07 PM
Hello Carlos,
I'm afraid that we can't diagnose and fix the problem you are experiencing without having a repository that we can access to debug Icenium's Clone implementation. Maybe if you provide us with access to such temporary repository we can narrow the problem and find a solution or workaround.
Greetings,
Ilian Iliev
the Telerik team
I'm afraid that we can't diagnose and fix the problem you are experiencing without having a repository that we can access to debug Icenium's Clone implementation. Maybe if you provide us with access to such temporary repository we can narrow the problem and find a solution or workaround.
Greetings,
Ilian Iliev
the Telerik team