Bugzilla – Full Text Bug Listing
| Summary: | Move core repository to platform | ||
|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Jonas Helming <jhelming> |
| Component: | Tools | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | denis.roy, Lars.Vogel, webmaster |
| Version: | 0.17 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows NT | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 452061 | ||
|
Description
Jonas Helming
Which repo? Sorry, forgot the link: https://git.eclipse.org/r/#/admin/projects/e4/org.eclipse.e4.tools.core Not that I don't trust what you're doing, but can we get someone on platform to +1 this? It would help me sleep better at night. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=452061 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=452693 As an example, Lars has +1 it +1 for the move to platform, this was suggested by the PMC I'm not entirely sure how to move a project that is enabled for Gerrit. I can't assume that simply mv'ing the directory will actually work. Matt do you know something I don't? I agree we'd need to do more than just move things in the filesystem. I found a post[1] by Shawn P. that may indicate where we need to change the DB(although he was splitting data). A quick tour of Google turned up this[2] which links to a code patch here[3], so they do appear to be 'working on it', in some fashion -M. [1]https://groups.google.com/d/msg/repo-discuss/jbhIe4sIUZo/8g3J773avgQJ [2]http://code.google.com/p/gerrit/issues/detail?id=560 [3]https://gerrit-review.googlesource.com/#/c/42247/ Is there anything, we can help with? Are there any news on this? Sorry to push a little bit, the development of the e4 core tools is blocked by the whole procedure (including preparation) since 4 weeks now. This is of course not your fault, but it would be great to have an accessible repo and the integration in the platform build asap. Thanks! Sorry, this is the first time we move a Gerrit repo. We don't want to just rush through it and screw everything up. So here's what I think needs to happen. Once I've done it in this bug we'll document the process internally. This was a good resource: https://groups.google.com/forum/#!topic/repo-discuss/ltIxBipUPKI a) have $oldprojectname and $newprojectname figured out. This is typically the path beyond /gitroot/gerrit, and typically looks like "e4/org.eclipse.e4.tools.core.git" In this case: $oldprojectname = "e4/org.eclipse.e4.tools.core" $newprojectname = "platform/org.eclipse.e4.tools.core" b) validate: SELECT * FROM changes where dest_project_name = "$oldprojectname" c) if correct: update changes set dest_project_name = "$newprojectname" where dest_project_name = "$oldprojectname" UPDATE ACCOUNT_PROJECT_WATCHES SET PROJECT_NAME='$newprojectname' WHERE PROJECT_NAME='oldprojectname'; UPDATE CHANGES SET DEST_PROJECT_NAME='projecttorename.new' WHERE DEST_PROJECT_NAME='projecttorename.old'; d) cd /gitroot; mv $oldprojectname.git $newprojectname.git e) Move/recreate the symlink: cd /gitroot/gerrit; rm $oldprojectname.git then create the new one in the correct location f) ssh -p 29418 adminusername@gerrit-hostname gerrit flush-caches --all g) Reindex Gerrit Stop Gerrit. java -jar /home/gerrit/review_site/bin/gerrit.war reindex -d /home/gerrit/review_site Start Gerrit. 7. Update permission inheritance (Rights Inherit From), if necessary Web UI > Projects > Select projecttorename.new > Access > Edit 8. Optional: Clone project To verify your project was renamed, clone it (projecttorename.new) to your local machine. Oddly, this project did not have any Gerrit changes, so there was nothing to do there. So the new project is now here: https://git.eclipse.org/r/#/admin/projects/platform/org.eclipse.e4.tools.core Do you wish to rename it, or keep it like that? Great, thank you! The name be kept (IMHO). There are no gerrit changes, because the repo was created from scratch and I only committed the bundles to be moved (including their history). Can we close this issue? Yes, looks like we're done. Thank you for your patience. (In reply to Denis Roy from comment #13) > Do you wish to rename it, or keep it like that? Looking at the other repos in platform I think we should rename it. I opened Bug 459798 for the discussion. |