| Summary: | [Polarsys] Creation of new repositories for Capella extensions | ||
|---|---|---|---|
| Product: | Community | Reporter: | Christophe Gatti <christophe.gatti> |
| Component: | Git | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | benoit.langlois, denis.roy, jean.barata, matthieu.helleboid, stephane.bonnet |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Christophe Gatti
+1 Done. -M. Hi, I reopen this bug so as to ask you whether you could clone the contents (sources, branches, tags, etc.) of the capella/capella-addons repository to each repository newly created: * capella/capella-xmlpivot * capella/capella-basic-vp * capella/capella-xhtml-docgen * capella/capella-sss-transition So that I could delete unnecessary files in each repository and keep track of the history of the developments for those. Best regards, Christophe. Christophe, I can copy the exact contents of one repo to all four, so they would all be identical. You'd lose everything committed there since the creation of those new repos. Is that what you're asking for? (In reply to Denis Roy from comment #4) > Christophe, I can copy the exact contents of one repo to all four, so they > would all be identical. You'd lose everything committed there since the > creation of those new repos. > > Is that what you're asking for? Hi Denis, We will not push to capella-addons repository anymore. You can copy the exact contents of capella-addons repo to all four. But do not just copy please, clone it to all four in the sense we would not want to lose the history. Once it is done, I will update the different jobs on our HIPP. Then, I will ask for the deletion of the capella-addons repo in a next time. Best regards, Christophe. Hi Denis, Did you manage to copy the exact contents of the capella-addons repo to all four and keeping history? Best regards, Christophe. I've copied the addons repo four times, as requested: https://git.polarsys.org/r/#/admin/projects/?filter=capella Please let me know if that works for you. Hi Denis, While looking at the four repositories, they seem to be empty: https://git.polarsys.org/c/capella/capella-basic-vp.git/ https://git.polarsys.org/c/capella/capella-sss-transition.git/ https://git.polarsys.org/c/capella/capella-xhtml-docgen.git/ https://git.polarsys.org/c/capella/capella-xmlpivot.git/ Maybe something went wrong during the copy? Regards, Christophe. Christophe, Instead of copying the repo files, I have cloned the repo into the four new ones. That seems to work better. Hi Denis, I just checked, the "clone" action worked, however only the "master" branch has been cloned. Could you please do the same with "v1.0.x" and "v0.8.x" branches? Best regards, Christophe. This seems to look better: http://git.polarsys.org/c/capella/capella-basic-vp.git/ I did: polarsys:/gitroot/capella# git clone --bare capella-addons.git capella-xhtml-docgen.git cd capella-addons.git git push --mirror ../capella-xhtml-docgen.git I did get one error: ! [remote rejected] refs/notes/review -> refs/notes/review (hook declined) Not sure if you need that refspec or not? Hi Denis, Did you try using git clone with --mirror option? We now see the branches v0.8.x and v1.0.x in each repository, that's great! Moreover, could you please make the Gerrit repository capella-addons readonly? So that we will keep the records of our reviews but we will use Gerrit for each repository. Regards, Christophe. I've made capella-addons read-only as requested. Closing as FIXED; please reopen if you need anything. (In reply to Denis Roy from comment #13) > I've made capella-addons read-only as requested. > > Closing as FIXED; please reopen if you need anything. Hi Denis, Thanks for the job done, it works perfectly now. Just a little thing to ask, could you please: - erase all contents in capella-xmlpivot (http://polarsys.org/c/capella/capella-xmlpivot.git/) repository; - clone again the capella-addons repo with the 3 branches (v0.8.x ; v1.0.x ; master) into it? Thanks, we made some mistakes while attempting to merge branches into this repo that's the reason why we would like to start with a clean slate. Regards, Christophe. Done. Please let me know if it works. Hi Denis. It's ok, thank you very much. Jean |