Community
Participate
Working Groups
In order to help with testing and eating our own dog food, it would make sense for us to use Gerrit on eclipse.org
Is this a duplicate of Bug 283749? Webmaster already has Gerrit on his list. I don't know what the expected timeline looks like. Is this something that can be done with a vserver? I do not want to replicate what EGit is doing, so anything running on a vserver would not--ideally--be the official project repo.
We could do this with a vserver temporarily. We could move the Gerrit connector pieces out of mylyn reviews to this vserver and do a similar workflow to what EGit/JGit is doing (until an official Gerrit server is ready for Eclipse)
(In reply to comment #2) > We could do this with a vserver temporarily. > > We could move the Gerrit connector pieces out of mylyn reviews to this vserver > and do a similar workflow to what EGit/JGit is doing (until an official Gerrit > server is ready for Eclipse) I have a terrible image of a dozen projects with their own vservers all running Gerrit. The one exception for EGit is easy to rationalize; rationalizing two gets harder. When I suggested a vserver, I was thinking of a Gerrit instance for testing, not one that would contain real code. Can mylyn.reviews test of out of the EGit Gerrit instance?
Setting up a Gerrit instance for testing shouldn't be difficult. Given that the vserver can handle the load we cut put it on mylyn.eclipse.org where we already have Bugzilla, Trac and Hudson test repositories. I guess the question is whether we could piggyback on egit.eclipse.org for hosting actual source code?
(In reply to comment #4) > I guess the question is whether we could piggyback on egit.eclipse.org for > hosting actual source code? No.
(In reply to comment #4) > Setting up a Gerrit instance for testing shouldn't be difficult. Given that the > vserver can handle the load we cut put it on mylyn.eclipse.org where we already > have Bugzilla, Trac and Hudson test repositories. Setting up a Gerrit for testing is very easy, close to setting up Hudson. But I think we are rather looking for a solution we can use for the project sources themselves. Just feels odd not to have Gerrit at hand after using it for 2 years for every change we did in EGit/JGit.
(In reply to comment #6) > Setting up a Gerrit for testing is very easy, close to setting up Hudson. But I > think we are rather looking for a solution we can use for the project sources > themselves. Just feels odd not to have Gerrit at hand after using it for 2 > years for every change we did in EGit/JGit. The EGit project has been good enough to provide us with a working install of Gerrit which has allowed us to explore the implications of its use on our infrastructure. Implementing Gerrit Eclipse-wide represents a significant amount of work for Webmaster, and--at least for now--hasn't managed to get to the top of his very full queue.
I'll mark this as a duplicate of bug 283749 since it looks we are getting close to having Gerrit for all projects on eclipse.org. *** This bug has been marked as a duplicate of bug 283749 ***
