incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <brond...@users.sf.net>
Subject [allura:tickets] #6463 Create code importer for Google Code
Date Tue, 23 Jul 2013 19:30:53 GMT
* http://code.google.com/p/msysgit/ which doesn't have a current git repo, still gets a repo
pulled in.
* why are we pulling in only trunk for SVN repos?  Seems like the whole thing would be better,
and perhaps even necessary to get a valid whole repo.
* I'd rather see 'code' instead of 'source' for the mount point & label, so it matches
what happens with new regular projects


---

** [tickets:#6463] Create code importer for Google Code**

**Status:** in-progress
**Labels:** import google-code 
**Created:** Mon Jul 15, 2013 04:31 PM UTC by Cory Johns
**Last Updated:** Tue Jul 23, 2013 05:02 PM UTC
**Owner:** Tim Van Steenburgh

During project import, SCM needs to be included.  Since Google Code only supports a single
repository at a time, we should just have a single Code Importer that checks the project to
discover the repo type and passes that information to the appropriate SCM tool's `clone_from_url`
method.

One way to discover the repo type would be to load `https://code.google.com/p/%s/source/browse/`
and get the text of the item `id="crumb_root"`, which will be one of `" git/ "`, `" hg/ "`,
or `" svn/ "`.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message