#667: Git: Initial clone should use "--depth 1" option
------------------------+---------------------------------------------------
Reporter: tfogal | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: undecided
Version: 0.7.11 | Resolution:
Keywords: git |
------------------------+---------------------------------------------------
Comment(by marcusl):
IIUC, this is similar to some discussion we had on Mercurial, where we
decided to keep the full repo on disk between update, but for clobber
mode, just retrieve the specified. For git, cloning shallow in clobber
mode makes sense, in update, not as much.
(I also think that it'd be cool to write something that would allow a
buildslave to cache DVCS:es locally, outside the build.dir, then do hard-
link clone into the buld dir. That would reduce bandwidth usage between
slave and repo servers, but still have access to the full history
locally.)
--
Ticket URL: <http://buildbot.net/trac/ticket/667#comment:3>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
