[Twisted-Python] Twisted bzr mirror (Was: Twisted Project Jobs Volunteer)

exarkun at twistedmatrix.com exarkun at twistedmatrix.com
Mon Jul 11 05:30:07 MDT 2011

On 9 Jul, 10:46 am, adi at roiban.ro wrote:
>On Fri, 2011-07-08 at 16:20 +0000, exarkun at twistedmatrix.com wrote:
>>On 7 Jul, 04:25 pm, adi at roiban.ro wrote:
>> >Pulling a single branch takes about 15 seconds, so maybe we the SVN
>> >repo
>> >can have some commit hooks to execute 'bzr pull' in the right branch.
>>I think getting the right hook set up to update just the right branch 
>>what we want to focus on.  Presently svn and bzr are hosted on the 
>>machine, which perhaps we can continue since this should bring the
>>overhead of mirroring down.  There is even a little code in 
>>trac-integration for determining which branch a changeset is on (at
>>least for the branch creation changeset) which might help.
>> >Please let me know what do you think should be the next action for
>> >resolving the bzr mirror issues?
>>Do you think you can put together something to run from an svn post-
>>commit hook to update just the single corresponding bzr branch?
>Yes. I will write the svn hooks for creating, updating and deleting the
>mirrored branches.
>>Meanwhile I can try your synchronization code to see if it has better
>>results than the current bzr svn-import based approach.
>You can also try to run a 5 minutes cron job for pulling just the 
>and another job for pulling each branch.

I ran this (all-branches version) a few times over the weekend.  The 
first time, when there was lots of catching up to do, took about 3.5 
hours.  After that, it was about 30 minutes per run.  This does seem 
fast enough to do nightly, so I'll set that up until we have the push- 
based version.


More information about the Twisted-Python mailing list