Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 495455

Summary: Migrate GEF repositories to GitHub (after Neon release)
Product: [Tools] GEF Reporter: Alexander Nyßen <nyssen>
Component: MiscAssignee: Alexander Nyßen <nyssen>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 0.2.0   
Target Milestone: 5.0.0 (Oxygen) M1   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 495768    
Bug Blocks:    

Description Alexander Nyßen CLA 2016-06-04 04:10:03 EDT
As agreed on by the project team we should migrate our code base from git.eclipse.org to GitHub (after the Neon release), replacing the up to now mirrored repositories there. I have started a discussion on the ged-dev mailing list to clarify the detailed procedure.
Comment 1 Alexander Nyßen CLA 2016-06-09 03:39:26 EDT
I raised bug #495768 against the foundation to initiate the GitHub migration directly after the Neon release. In it have provided exact details on how the migration is to be performed.
Comment 2 Alexander Nyßen CLA 2016-06-14 02:06:50 EDT
We will also have to update the source references in our code base accordingly after it has been transferred.
Comment 3 Alexander Nyßen CLA 2016-06-27 04:16:16 EDT
We will have to update the CONTRIBUTING files, the meta-data, as well as the adopter and contributor guides, as soon as the migration is done.
Comment 4 Alexander Nyßen CLA 2016-07-08 03:27:42 EDT
And after having updated our build jobs at hudson.eclipse.org/gef, they do no longer run because they can't connect to GitHub (see below). Can you please take a look?

Started by user nyssen@itemis.de
Building remotely on hippcentos
Checkout:gef4-master / /opt/users/genie.gef/workspace/gef4-master - hudson.remoting.Channel@f1278b4:hippcentos
Using strategy: Default
Git Exe: git
Last Built Revision: Revision f9f61d38e9cb66822d325280c06bd1e61da371f4 (origin/master)
Checkout:gef4-master / /opt/users/genie.gef/workspace/gef4-master - hudson.remoting.LocalChannel@6f749b46
Fetching changes from the remote Git repository
Fetching upstream changes from https://github.com/eclipse/gef.git
ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway
hudson.plugins.git.GitException: Error performing command: git fetch -t https://github.com/eclipse/gef.git +refs/heads/*:refs/remotes/origin/*
Command "git fetch -t https://github.com/eclipse/gef.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: fatal: unable to access 'https://github.com/eclipse/gef.git/': Failed connect to github.com:443; Connection timed out

	at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:831)
	at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:793)
	at hudson.plugins.git.GitAPI.fetch(GitAPI.java:213)
	at hudson.plugins.git.GitAPI.fetch(GitAPI.java:1047)
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:1828)
	at hudson.plugins.git.GitSCM.access$900(GitSCM.java:107)
	at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1061)
	at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1024)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2059)
	at hudson.remoting.UserRequest.perform(UserRequest.java:107)
	at hudson.remoting.UserRequest.perform(UserRequest.java:41)
	at hudson.remoting.Request$2.run(Request.java:276)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: hudson.plugins.git.GitException: Command "git fetch -t https://github.com/eclipse/gef.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: fatal: unable to access 'https://github.com/eclipse/gef.git/': Failed connect to github.com:443; Connection timed out

	at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:824)
	... 16 more
ERROR: Could not fetch from any repository
FATAL: Could not fetch from any repository
hudson.plugins.git.GitException: Could not fetch from any repository
	at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1068)
	at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1024)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2059)
	at hudson.remoting.UserRequest.perform(UserRequest.java:107)
	at hudson.remoting.UserRequest.perform(UserRequest.java:41)
	at hudson.remoting.Request$2.run(Request.java:276)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Comment 5 Alexander Nyßen CLA 2016-07-09 04:50:10 EDT
It seems there is only a problem with the gef repo, the gef-legacy works fine.
Comment 6 Alexander Nyßen CLA 2016-07-10 02:53:26 EDT
(In reply to Alexander Nyßen from comment #5)
> It seems there is only a problem with the gef repo, the gef-legacy works
> fine.

Opened bug #497617 to keep track of the checkout problem (I hit the wrong bug here, wanted to notify webmaster via bug #495768).
Comment 7 Alexander Nyßen CLA 2016-07-13 02:28:32 EDT
Checkout now seems to be possible, while the build still struggle with problems downloading artifacts. Maybe this is related to the recent mirror problems. We'll see...

Something else: I have tried to set up a Travis CI build for our project. My goal would be to have an automated CI build that gets executed when a new pull-request is received. According to Travis I need admin rights on the repos to enabled the necessary hooks. Would it be ok to add Travis? Just to clarify, I am not intending to replace the CI build on the GEF HIPP, its just that I want to be able to have a build that automatically runs when a pull-request is added.
Comment 8 Alexander Nyßen CLA 2016-07-17 08:02:10 EDT
It seems the download problems are related to Tycho and the Neon repository. Switched the gef-legacy build to use Tycho 0.25.0.
Comment 9 Alexander Nyßen CLA 2016-07-17 08:02:59 EDT
Updated the gef and ged-legacy releng pom's to use the GitHub urls for the tycho.scmUrls.
Comment 10 Alexander Nyßen CLA 2016-07-17 08:12:18 EDT
I further had to remove -Dorg.eclipse.update.jarprocessor.pack200="/shared/common/sun-jdk1.6.0_21_x64/jre/bin" to get the legacy-build run against a Neon target.
Comment 11 Alexander Nyßen CLA 2016-08-14 07:42:14 EDT
I think we are done here. The contributing files have been adjusted as part of bug #498538. Resolving as fixed in 5.0.0 M1.