[Buildbot-devel] mixing baseURL and svnurl in a factory?

Marcus Lindblom macke at yar.nu
Thu Apr 30 18:29:09 UTC 2009

Christian Unger wrote:
> my builder throws an exception when set up like so:
> f=factory.BuildFactory([
> 	source.SVN(svnurl=externalDependencyURL', workdir='./build/ 
> Dependency1')
> 	source.SVN(baseURL=internalURL, defaultBranch='trunk', workdir='./ 
> build/projectUsingDependency1')
> ])
> on my ForceBuild page I specify a branch and honestly I would not  
> expect the first svn-step to freak out on the optional branch parameter:
>>   File "/Library/Python/2.5/site-packages/buildbot-0.7.10p1- 
>> py2.5.egg/buildbot/process/buildstep.py", line 710, in _startStep_2
>>     skip = self.start()
>>   File "/Library/Python/2.5/site-packages/buildbot-0.7.10p1- 
>> py2.5.egg/buildbot/steps/source.py", line 184, in start
>>     self.startVC(branch, revision, patch)
>>   File "/Library/Python/2.5/site-packages/buildbot-0.7.10p1- 
>> py2.5.egg/buildbot/steps/source.py", line 462, in startVC
>>     assert not branch # we need baseURL= to use branches
>> exceptions.AssertionError:
> I would rather expect the first step to ignore the specified branch.

I think the branch comes from the changesource, so I'm not sure if you 
can ignore that.

Perhaps a shell-command for the first source-step would be better, as it 
is independent from the branch you get in the change?

> How are you guys setting this up for multiple branches using the same  
> dependency from a different repository url?

Haven't tried that one. Do you expect to trigger build from changes in 
different repos? That's unfortunately not well supported in the current 

I once hacked something together with SVN that made it work anyway, as 
all repositories where on the same server and thus hade the same 
"baseurl", even though different "branches" actually where in different 

I.e. the branches from checkins where called 'repo1/trunk' or 
'repo2/trunk', which made things work pretty well.


More information about the devel mailing list