Bugzilla – Full Text Bug Listing
| Summary: | Document Git/Gerrit setup for Eclipse Platform projects (direct push to Git repo) | ||
|---|---|---|---|
| Product: | Community | Reporter: | Markus Keller <markus.kell.r> |
| Component: | Git | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert, denis.roy, krzysztof.daniel, thanh.ha |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
|
Description
Markus Keller
(In reply to comment #0) > Necessary common requirements seem to be: > - don't touch permissions in /gitroot/<repo> > - change the Project Options from "Merge If Necessary" to "Fast Forward Only" Instead of changing permissions on /gitroot/<repo> for platform we are using ACLs to add the Gerrit user leaving existing permissions untouched. Is this really an issue? I think we found a way to solve this using only Gerrit permissions already via discussions in bug 418966. I would argue that platform developers should stop using the regular Git URLs altogether and use only the Gerrit URLs. I think the only user that might still need this URL is e4build but we can add e4build into Gerrit Permissions for the platform repos too so that it doesn't need to use the regular SSH URLs. (In reply to Thanh Ha from comment #3) > I think we found a way to solve this using only Gerrit permissions already > via discussions in bug 418966. I would argue that platform developers should > stop using the regular Git URLs altogether and use only the Gerrit URLs. > > I think the only user that might still need this URL is e4build but we can > add e4build into Gerrit Permissions for the platform repos too so that it > doesn't need to use the regular SSH URLs. We - the Eclipse project - want to own our repos and be able to use Git in the normal/default way and also be able to access our repos via SSH (for those with shell access). The status quo is fine and no pressure/request to change this. (In reply to Dani Megert from comment #4) > (In reply to Thanh Ha from comment #3) > > I think we found a way to solve this using only Gerrit permissions already > > via discussions in bug 418966. I would argue that platform developers should > > stop using the regular Git URLs altogether and use only the Gerrit URLs. > > > > I think the only user that might still need this URL is e4build but we can > > add e4build into Gerrit Permissions for the platform repos too so that it > > doesn't need to use the regular SSH URLs. > > We - the Eclipse project - want to own our repos and be able to use Git in > the normal/default way and also be able to access our repos via SSH (for > those with shell access). The status quo is fine and no pressure/request to > change this. FWIW I didn't intend on forcing any changes. I wanted to point out that we were able to come up with a Gerrit permission set which provided similar settings to what Platform Git Hooks provided. Also in case you were not aware Gerrit does have an SSH port too. (In reply to Thanh Ha from comment #5) > Also in case you were not aware Gerrit does have an SSH port too. I know. My point was more regarding the shell access. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. As we move towards using jGit instead of git, we won't consider this. |