[Buildbot-commits] [Buildbot] #2490: Scheduler build clones head instead of revision from previous build in multi-repo setup

[Buildbot trac]

#2490: Scheduler build clones head instead of revision from previous build in
multi-repo setup
----------------------+------------------------
Reporter:  thedylman  |      Owner:
    Type:  defect     |     Status:  new
Priority:  major      |  Milestone:  0.8.8
 Version:  0.8.7p1    |   Keywords:  schedulers
----------------------+------------------------
 The setup is:
   Builder Y with mercurial repos A and B.
   SingleBranchScheduler with codebases for A and B.

 The steps:
   Commit with id 5 to repo A.
   After treeStableTimer finishes build is queued on builder Y and waiting
 for slave.
   Commit with id 3 to repo B.
   Builder Y starts build/clone step with change for repo A and head for
 repo B.

 The problem is repo B is updating to head because revision id is set to
 None. Instead it should update to the revision id 2 from the previous
 build on builder Y.

 In a single repo setup the sourcestamp always has a change so it updates
 to the revision id of that change. For a multirepo setup only repos with
 changes have the revision field set, so all other repos are updated to
 head which then includes changes that are not listed in the sourcestamps.

 The effects of this is the web interface and emails do not show the
 correct changes and users for a build.

-- 
Ticket URL: <http://trac.buildbot.net/ticket/2490>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation