[Buildbot-devel] Triggers receiving wrong branch info

René Müller mue.r at gmx.de
Wed May 20 07:37:09 UTC 2009


Michael Rubinsky schrieb:
> I setup our buildbot to use triggers to setup dependencies for 
> particular builds.  I have a SVN repository that contains all my 
> projects.  I'm using svn_buildbot.py to trigger my builds via svn 
> commits.  The problem is, that when Build A Triggers Build B, Build B is 
> getting the branch / path information from Build A, which in turn either 
> pulls down the wrong repository or sends an invalid branch.
> 
> [snip]

I had the same problem and solved it like this:

Repo-Layout:

Project1/trunk
Project1/branch
Project1/releases
Project2/trunk
Project2/branch
Project2/releases

--------------------
svn_source = SVNPoller("https://my.repo/data/svn/Project1",\
                       svnuser=const_svnuser, svnpasswd=const_svnpasswd,\
                       split_file=my_split_file,\
                       pollinterval=const_pollinterval)
c['change_source'].append(svn_source)

sch_Project1 = RepositoryScheduler(name="Project1",
                                   branches=None,
                                   treeStableTimer=defaultTreeStableTime,
                                   builderNames=["Project1"])
c['schedulers'].append(sch_Project1)

sch_Project2_trig = Triggerable(name="Project2_trig",\
                                builderNames=["Project2"])
c['schedulers'].append(sch_Project2_trig)

--------------------
in builder Project1:

stepList.append(Trigger(schedulerNames=["Project2_trig"], waitForFinish=True, updateSourceStamp=False))

--------------------
This works fine for me, if every branch that exists in Project1 is present in Project2 and you don't use the try scheduler. This fails, because it tries to apply the patch on both projects. I think
the important part is "updateSourceStamp" in the trigger step.


Cheers,
René





More information about the devel mailing list