[Buildbot-commits] [SPAM] Re: [Buildbot] #865: buildbot try not working with mercurial

[Buildbot]

#865: buildbot try not working with mercurial
----------------------+-----------------------------------------------------
Reporter:  bgunnison  |       Owner:        
    Type:  defect     |      Status:  new   
Priority:  blocker    |   Milestone:  0.8.1 
 Version:  0.8.0      |    Keywords:  hg try
----------------------+-----------------------------------------------------

Comment(by bgunnison):

 Replying to [comment:3 marcusl]:
 > Correct. The try was written before DVCS:es, so it doesn't check for
 non-pushed commits, which it should.
 >
 > We need to decide whether to:
 >
 >  * send the missing changesets + patch, and optionally clean/strip the
 slave-repo afterwards
 >  * or, just send one large patch between the user's repo and the slave's
 'nearest' revision.
 >
 > Patches welcome. I think this is a good thing to get fixed. :)

 I was thinking of using hg bundle/unbundle

 1) Determine Master rep (MR) common ancestor with Working Repo (WR). This
 produces a CAR (Common Ancestor Revision)
 2) do "hg bundle" in WR to package changes since CAR
 3) Send CAR and bundle to Build Slave (BS)
 4) BS Clones MR to CAR then applies bundle (this is just like a push) and
 will exactly replicate WR.

 I like the bundle approach as a compressed set of diffs is reliable over
 networks. An error in text diffs can be very bad.

 Thoughts?

-- 
Ticket URL: <http://buildbot.net/trac/ticket/865#comment:4>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation