#1915: GitPoller stops on wrong revision while fetching buildbot repo at the
first
time.
-----------------------+--------------------
Reporter: jollyroger | Owner:
Type: defect | Status: new
Priority: minor | Milestone: 0.8.4
Version: 0.8.3p1 | Resolution:
Keywords: git |
-----------------------+--------------------
Changes (by dustin):
* keywords: gitpoller, git => git
* milestone: undecided => 0.8.4
Comment:
The first time the gitpoller is started, it should just do a fetch, and
after that pull and generate Change objects. My guess is that the working
directory already existed in this case, and was hundreds of revisions
behind. In that case, at each run the gitpoller will process a limited
number of changes (100, IIRC). So I think you're seeing expected
behavior..
--
Ticket URL: <http://trac.buildbot.net/ticket/1915#comment:1>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
