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

Bug 392126

Summary: Enable Gerrit for OSEE project
Product: Community Reporter: Roberto Escobar <roberto.e.escobar>
Component: GitAssignee: Eclipse Webmaster <webmaster>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: donald.g.dunne, roberto.e.escobar, ryan.d.brooks
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Roberto Escobar CLA 2012-10-16 18:10:26 EDT
Hi Webmaster, 

The OSEE project would like to start using Gerrit. The project repository can be accessed through https://git.eclipse.org/gitroot/osee/org.eclipse.osee.git. 

Initially, we would like committers to be able to bypass the Gerrit code review system if necessary and push changes directly to the git repository (using the new URLs).

Thanks,
Roberto
Comment 1 Eclipse Webmaster CLA 2012-10-17 14:22:27 EDT
Ryan or Donald, can I get a +1 here?

-M.
Comment 2 Ryan Brooks CLA 2012-10-17 14:48:05 EDT
+1 for using Gerrit.

Will it be easy to later switch the configuration such that all commits must go through Gerrit?

Thanks,
Ryan
Comment 3 Eclipse Webmaster CLA 2012-10-17 15:37:59 EDT
I've enabled Gerrit for osee/org.eclipse.osee.git.  You can add it to the list of projects you watch:

https://git.eclipse.org/r/#/settings/projects

Upload your SSH public keys to Gerrit if you wish to use SSH:
https://git.eclipse.org/r/#/settings/ssh-keys

Your Gerrit-enabled repo URLs:
ssh://userid@git.eclipse.org:29418/osee/org.eclipse.osee.git
https://git.eclipse.org/r/p/osee/org.eclipse.osee.git

Gerrit@Eclipse docs:
http://wiki.eclipse.org/Gerrit#Logon

We should be able 'require' Gerrit by removing the push permission in future.

-M.
Comment 4 Roberto Escobar CLA 2012-10-18 17:35:42 EDT
How do we handle rebasing and removal of in-work topic branches now that the OSEE git repository is managed by Gerrit? 

Before, committers were able to perform a remote branch deletion (git push origin :topic_branch) or a force push (git push -f origin topic_branch) to update in- work branches.
Comment 5 Eclipse Webmaster CLA 2012-10-23 13:49:13 EDT
I'm not really sure, but I think you can still do that as long as you have the 'push' permission.

Your best bet may be to ask the Gerrit folks.

-M.
Comment 6 Roberto Escobar CLA 2012-10-25 19:26:44 EDT
Hi, 

After testing permission settings on a local Gerrit instance we would like the following permissions granted to the technology.osee group for the osee/org.eclipse.osee project:

For the "Push" permission we need the "Force Push" box checked. We also need this for the "Push Annotated Tag" permission. Finally, we need "Forge Author Identity" enabled for the "refs/tags/*" section.

Thanks, 
Roberto
Comment 7 Eclipse Webmaster CLA 2012-10-26 14:19:37 EDT
Done.

-M.
Comment 8 Roberto Escobar CLA 2012-11-02 19:20:41 EDT
Hi, 

For the osee/org.eclipse.osee project, can we have general->project options set to fast-forward only instead of merge if necessary. 

Thanks, 
Roberto
Comment 9 Eclipse Webmaster CLA 2012-11-05 10:53:53 EST
Done.

-M.
Comment 10 Roberto Escobar CLA 2012-11-06 18:37:02 EST
Hi, 

Seems we lost all previous permission settings after the last change.
Can we have those settings restored?

Thanks, 
Roberto
Comment 11 Denis Roy CLA 2012-11-07 09:10:00 EST
That was bug 393735 -- apologies for that.
Comment 12 Roberto Escobar CLA 2012-11-08 14:41:50 EST
I am not sure if I should post here or to the bug listed above, but we are still unable to push changes to our repo. Any updates?
Comment 13 Denis Roy CLA 2012-11-08 14:48:49 EST
Are you using https?  Any specific error?
Comment 14 Roberto Escobar CLA 2012-11-08 15:13:26 EST
I am trying to push a new branch to origin = https://git.eclipse.org/r/p/osee/org.eclipse.osee.git. I get the following:

$ git push origin 0.10.4
Counting objects: 65, done.
Delta compression using up to 12 threads.
Compressing objects: 100% (17/17), done.
Writing objects: 100% (38/38), 5.77 KiB, done
Total 38 (delta 15), reused 25 (delta 6)
error: RPC failed; result=22, HTTP code = 500
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly