Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 325857 - EGit and JGit need to move to the new hudson
Summary: EGit and JGit need to move to the new hudson
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-21 10:01 EDT by Chris Aniszczyk CLA
Modified: 2010-09-21 17:37 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Aniszczyk CLA 2010-09-21 10:01:05 EDT 
The job names were pretty much "egit" and "jgit" if I recall
Comment 1 Benjamin Muskalla CLA 2010-09-21 10:30:14 EDT 
There was also a jgit-gerrit job, not sure what the intention of it was. Shawn, do we still need that one?
Comment 2 Shawn Pearce CLA 2010-09-21 10:36:03 EDT 
(In reply to comment #1)
> There was also a jgit-gerrit job, not sure what the intention of it was. Shawn,
> do we still need that one?

I think they were trying to use one of the Hudson-Gerrit integration plugins
to automatically test changes that were uploaded to Gerrit.  Not sure what the
status of that is...
Comment 3 Matthias Sohn CLA 2010-09-21 12:14:34 EDT 
The idea was to run the gerrit hudson plugin which enables to run build and tests on the changes proposed for review before they get merged into master.

for that we would need 
- the gerrit hudson plugin installed on Hudson
- a gerrit user for the hudson plugin so that it can vote on proposed changes
- a new "Verified" voting category in gerrit

Whenever a new change is proposed the job will run the build and tests and if they succeed vote +1 on "Verified" category if the build fails it will vote -1 and link back to the failed builds page in hudson. 

I think this would be cool as it would sort out changes which break the build or tests. We use that plugin at SAP and most projects want to use it. On the other end of the equation this of course creates some additional load for the build server.
Comment 5 Chris Aniszczyk CLA 2010-09-21 15:47:57 EDT 
I guess we lose our old builds right? I guess that's OK...
Comment 6 Chris Aniszczyk CLA 2010-09-21 15:48:39 EDT 
Oh... looks like a firewall issue?

$ git clone -o origin git://egit.eclipse.org/jgit.git /opt/users/hudsonbuild/.hudson/jobs/jgit/workspace
ERROR: Error cloning remote repo 'origin' : Could not clone git://egit.eclipse.org/jgit.git
ERROR: Cause: Error performing git clone -o origin git://egit.eclipse.org/jgit.git /opt/users/hudsonbuild/.hudson/jobs/jgit/workspace
Command returned status code 128: fatal: Unable to look up egit.eclipse.org (port 9418) (Name or service not known)
Initialized empty Git repository in /opt/public/jobs/jgit/workspace/.git/

Trying next repository
ERROR: Could not clone repository
FATAL: Could not clone
hudson.plugins.git.GitException: Could not clone
	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:719)
	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:658)
Comment 7 Denis Roy CLA 2010-09-21 15:52:11 EDT 
Internal DNS .. I'm on it.
Comment 8 Denis Roy CLA 2010-09-21 16:27:49 EDT 
> Internal DNS .. I'm on it.

Should be cleared up ... please try now.
Comment 9 Chris Aniszczyk CLA 2010-09-21 17:37:59 EDT 
Things look OK.

We have some build issues to debug on our end.