About Github migration

Charles Crouch ccrouch at redhat.com
Tue Sep 25 18:56:58 UTC 2012



----- Original Message -----
> Maybe we should watch our fellows at JBoss Tools doing their SVN
> migration and
> repository splitting so that we can learn from their mistakes ;)
> 
> https://github.com/maxandersen/jbosstools-gitmigration
> 
> Also, I do believe the split should be more granular than plugins and
> the rest
> of the codebase - at least core, agent plugins, server plugins,
> scripting,
> server.
> 
> Then we have the opportunity for example to move dbutils out of core
> where it
> really doesn't belong, because nothing but server needs it and
> potentially
> other changes.
> 

How much of this reorganizing should we bite off as part of the github migration?
Is it easier/harder to do this now versus wait until we've moved over?


> IMHO, the logistics of the migration is going to be much simpler than
> the
> preparation steps of modifying the build and actually deciding on the
> granularity of the repo split. This is a discussion we did not have
> yet though
> - at least not one where we'd come to an agreement on an action plan
> ;)

+1 I agree we need a plan.

> 
> Lukas
> 
> 
> On Friday, September 21, 2012 16:44:03 Heiko W.Rupp wrote:
> > Hi,
> > 
> > to get some experience I tried how some migration to github might
> > look like.
> > I did that with my personal GitHb account, so this is not available
> > in
> > github/rhq-project (yet)
> > 
> > ** First I basically followed the answer to this question on stack
> > overflow
> > to pull stuff from FH and pushed to GH
> > 
> > http://stackoverflow.com/questions/5181845/git-push-existing-repo-to-a-new-a
> > nd-different-remote-repo-server
> > 
> > I think for a real migration we would first do a
> > 
> > git fetch --all
> > git remote add github <github url>
> > and then a
> > git push --mirror github
> > 
> > This should copy the whole repository inc. all branches and tags.
> > 
> > We may consider pruning old tags and branches here - especially as
> > the FH repo is not going away.
> > 
> > ** Then I went and cloned the repo locally and followed
> > http://stackoverflow.com/a/359759/100957
> > 
> > to separate out the modules/plugins directory into its own repo.
> > Created a new repo on github rhq-plugins and pushed the
> > plugins to this new repo
> > 
> > ** In the third step I cloned the github rhq repository and
> > followed the first comment to
> > http://stackoverflow.com/a/955793/100957
> > to clean out the plugins from above rhq repository and tried to
> > push the
> > result to github. This whole locally cleaning  "took ages"
> > 
> > The push failed, as the local repo and the remote have diverged.
> > One can use -f here to forcibly push (which I've done)
> > Or in an earlier step not push the rhq repo until after the
> > split-off of the
> > plugins. Or in the main repo just rm -r && git rm on the plugins
> > and have
> > the removal recorded in the history. This may even be faster than
> > pruning
> > that directory hierarchy out.
> > 
> > 
> > Results are now at
> > https://github.com/pilhuhn/rhq
> > and
> > https://github.com/pilhuhn/rhq-plugins
> > 
> >    Heiko
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
> 


More information about the rhq-devel mailing list