Support project export for eclipselabs.org

[GoogleCodeExporter]

Currently you cannot export projects under /a/eclipselabs.org. This feature is 
in-progress. This bug is for tracking purposes.

Original issue reported on code.google.com by chrsm...@google.com on 13 Mar 2015 at 11:18

[GoogleCodeExporter]

Original comment by chrsm...@google.com on 13 Mar 2015 at 11:26

[GoogleCodeExporter]

Issue 17 has been merged into this issue.

Original comment by chrsm...@google.com on 14 Mar 2015 at 6:38

[GoogleCodeExporter]

Original comment by chrsm...@google.com on 14 Mar 2015 at 6:39

[GoogleCodeExporter]

I've my project under "https://code.google.com/a/eclipselabs.org/p/logviewer/" 
and there is a button "Export to GitHub". The process can be started and also 
there is new repo "https://github.com/anb0s/logviewer" with one initial commit 
and email message about "Export Complete".

Original comment by andre.bo...@anbos.de on 15 Mar 2015 at 2:27

[GoogleCodeExporter]

@andr: That's because there is a project called logviewer in the default (not 
eclipselabs.org) namespace: https://code.google.com/p/logviewer - it was 
converted instead of yours.

Original comment by harmathdenes on 15 Mar 2015 at 5:41

[GoogleCodeExporter]

Original comment by chrsm...@google.com on 15 Mar 2015 at 6:12

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Issue 38 has been merged into this issue.

Original comment by chrsm...@google.com on 15 Mar 2015 at 6:28

[GoogleCodeExporter]

@harmathdenes: thanks for the info! so export from eclipselabs.org is not 
possible.
I've deleted the wrong imported project "https://github.com/anb0s/logviewer" 
and created one with different name 
"https://github.com/anb0s/eclipse-logviewer" for my experiments with manual 
migration (https://code.google.com/p/support-tools/wiki/MigratingToGitHub).

So if export from eclipselabs.org will be supported i will try it again...

Original comment by andre.bo...@anbos.de on 15 Mar 2015 at 7:47

[GoogleCodeExporter]

code import was easy, but issues are not possible, because Google Takeout is 
not available for me :( need the automatic solution for eclipselabs.org export 
to GitHub...

Original comment by andre.bo...@anbos.de on 15 Mar 2015 at 8:16

[GoogleCodeExporter]

Issue 53 has been merged into this issue.

Original comment by chrsm...@google.com on 23 Mar 2015 at 5:16

[GoogleCodeExporter]

Until this is resolved, the Export to GitHub button should be disabled because 
it exports the wron project!

Original comment by harmathdenes on 24 Mar 2015 at 9:08

[GoogleCodeExporter]

What about this feature now? It was promised for the week from 16th of March in 
Issue 38. Can you give a rough estimation?

Original comment by konra...@gmx.de on 31 Mar 2015 at 11:01

[GoogleCodeExporter]

Sorry for the delay in getting this feature out there, unfortunately I've been 
swamped. I can confirm that I've started and have the first 90% finished... but 
I don't know how long until I get the _next_ 90% finished and rolled out. [1]

In the mean time, you can use our stand-alone tools for exporting your project 
to GitHub. Though I don't think it will take much more than a few more weeks.

[1] http://en.wikipedia.org/wiki/Ninety-ninety_rule

Original comment by chrsm...@google.com on 1 Apr 2015 at 5:25

[GoogleCodeExporter]

@Chris: Thanks for the status update! What exactly are the "stand-alone" tools 
you are mentioning?

Original comment by harmathdenes on 1 Apr 2015 at 9:25

[GoogleCodeExporter]

This has been fixed and rolled out. To export a project from eclipse-labs, add 
"eclipselabs.org:" as a prefix to the project name. For example, to export:
https://code.google.com/a/eclipselabs.org/p/cppcheclipse/

Enter "eclipselabs.org:cppcheclipse" as the project name.

As for the "stand-alone" tools, I was referring to the tools mentioned in this 
wiki post:
https://code.google.com/p/support-tools/wiki/MigratingToGitHub

Original comment by chrsm...@google.com on 14 Apr 2015 at 5:59

• Changed state: Fixed

[GoogleCodeExporter]

Could you fix the parametrisation of the GitHub exporter? Currently when 
clicking on "Export to Github" on 
https://code.google.com/a/eclipselabs.org/p/cppcheclipse/ the wrong project is 
gonna be exported and there is no possibility to set a prefix (the link 
https://code.google.com/export-to-github/export?project=cppcheclipse seems to 
be wrong). Only when the exporter is called manually via 
https://code.google.com/export-to-github/ it is possible to enter a prefix.

Original comment by konra...@gmx.de on 14 Apr 2015 at 6:11

[GoogleCodeExporter]

@konrad_w, good catch! I'll work on fixing that next. Sorry about the bug!

Original comment by chrsm...@google.com on 14 Apr 2015 at 6:12

[GoogleCodeExporter]

thanks, i've successfully exportet the project 
"https://code.google.com/a/eclipselabs.org/p/logviewer/" to GitHub!

Original comment by andre.bo...@anbos.de on 14 Apr 2015 at 8:01

[GoogleCodeExporter]

In my case (eclipselabs.org project Fastest) I was able to start the export, 
but the importer fails with error message: "There was an error pushing commits 
to GitHub."
I have tried to restart the import process several times but it still fails 
with the same error.
Any ideas?

Thanks

Original comment by crist...@rtfm.org.ar on 15 Apr 2015 at 1:46

[GoogleCodeExporter]

Re: "There was an error pushing commits to GitHub."

Unfortunately that error message is all we get, so I can't help you in 
diagnosing the problem. However, our colleagues at GitHub suggest that we ask 
people to contact GitHub's support at "https://github.com/contact". Please 
include the name of the target repository (e.g. https://github.com/user/repo), 
and they will be able to assist you from there.

Original comment by chrsm...@google.com on 15 Apr 2015 at 1:57

[GoogleCodeExporter]

FYI I was getting the error during import because my SVN repository contains a 
file larger than 100MB. There is a 100MB per file limit at GitHub.
They have sent me a guide explaining how to clean up the repository before 
importing.

Thanks again.

Original comment by crist...@rtfm.org.ar on 15 Apr 2015 at 7:06