Step Three: Click that same mentioned link.
Step Four: Locate and click the “Reset Repository” button.
Step Five: Smile, knowing you’re about to “stick it to the man” ;-)
Step Six: Using your own GoogleCode username in place of mine, the location of your projects repository on your local file system in place my projects file system location, and your newly created project on GoogleCode projects name in place of my projects name, run the following command from the machine in which your projects repository is located,
svnsync init --username xmlhacker file:///srv/svn/nuxleus https://nuxleus.googlecode.com/svn
Don’t have access to the machine your project SVN repository is hosted on? No problem. Just replace
file:///srv/svn/nuxleus with the network accessible svn://, http:// or https:// equivalent of your projects SVN root.
Step Six: With that process now complete, run the following, doing the same replacements mentioned above where appropriate,
svnsync sync --username xmlhacker https://nuxleus.googlecode.com/svn
Step Seven: Smile even bigger knowing “the man has just been stuck” with acting as a mirror for your projects SVN repository.
Step Eight: Stay tuned for the next installment of HGC, “[Hacking GoogleCode:Part Two] Using GoogleCode as Your Projects Main SVN Repository Without Having To Give Up Your Beloved Trac Project Management Interface To Instead Be Forced Into Using
The Man’s Broke A$$ Attempt at Implementing a Proper Bug Tracking and Feature Management System Much Like I Have w/ the nuXleus Project Repository Which Is Now Happily Hosted on GoogleCode While My Beloved Trac Project Management Interface Is Still Firmly In Place and In Sync With the Check In’s Made To The GoogleCode Repository” (or maybe a title that’s a slight bit shorter than this one. ;-)
Update: DO NOT CHECK IN A SINGLE NEW REVISION IN YOUR PROJECT’S PREVIOUS REPOSITORY IF YOU PLAN TO USE GOOGLECODE AS YOUR PRIMARY SVN REPOSITORY.
Instead, either check out a new working copy from GoogleCode or use
svn switch --relocate https://projectname.googlecode.com/svn from within your existing checked out working copy.
On the other hand, if you plan to use GoogleCode as a read only mirror (not really all that wise if you give read/write access to anyone other than yourself as, as far as I know, you can’t restrict check-ins to the GoogleCode repository past simply not adding any new project owners or developers),
DON’T CHECKOUT A SINGLE WORKING COPY FROM THE GOOGLECODE REPOSITORY USING https://. USE http:// ONLY OR FIND YOURSELF *REALLY* MAD WHEN YOU ACCIDENTALLY CHECK IN CHANGES TO YOUR “READ-ONLY” SVN REPOSITORY.