#2154: Master-side git source step breaks revision+shallow
----------------------+-----------------------------
Reporter: Tobi | Owner:
Type: undecided | Status: new
Priority: minor | Milestone: undecided
Version: 0.8.5 | Keywords: git master-side
----------------------+-----------------------------
Master-side git source step breaks situation of specifying shallow=True,
and then passing a revision property to a build request, that it hasn't /
won't fetch, due to the shallow clone.
Slave-side git source step would, with full builds, detect this situation
and do a "git init ; git fetch ..." instead.
E.g. this code in slave-side git source step:
{{{
#!python
# If they didn't ask for a specific revision, we can get away with
a
# shallow clone.
if not self.args.get('revision') and self.args.get('shallow'):
}}}
I'm not sure how slave-side git handled incremental builds in shallow
clones.
--
Ticket URL: <http://trac.buildbot.net/ticket/2154>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
