[Buildbot-devel] multiple dependent schedulers?

Axel Hecht l10n.moz at googlemail.com
Sun Aug 5 17:52:54 UTC 2007


I haven't looked at Dustin's code too closely, but maybe it'd be
easier to use his triggerable schedulers from
http://buildbot.net/trac/ticket/56?

I'm a tad sceptical at the abuse for branches.

The sign dep scheduler doesn't kick off because it's watching the
build scheduler, not the build dep scheduler.

I could play mind games about using build properties to control where
in the super build to start off, too, but that would likely require to
hack both the steps and the build class.

Axel

2007/8/5, Robert Helmer <robert at roberthelmer.com>:
> Hey,
>
> I'm trying to chain a bunch of steps together for release automation
> purposes, using dependent schedulers. It's getting pretty complicated (I've
> attached it to the end of this message), so I wonder if I'm missing
> something.. basically I have a ton of builders, some of them can run in
> parallel and some cannot. I am (ab)using "buildbot sendchange" to be able to
> kick off the initial run, and using "branch" to be able to trigger an
> arbitrary scheduler.
>
> I have a couple questions:
>
> 1) can I make this shorter and/or more readable?
> 2) sign_depscheduler isn't kicking off, did I misconfigure something here?
> build_depscheduler gets kicks off from tag_scheduler fine.
>
> Any general "wtf are you doing it this way, do this instead" comments warmly
> welcomed :)
>
>
> Thanks!
> Rob
>
> --
> c['schedulers'] = []
> tag_scheduler = Scheduler(name="tag", branch=None,
>                           treeStableTimer=0, builderNames=["tag"])
> build_scheduler = Scheduler(name="build", branch="build",
>                             treeStableTimer=0,
>                             builderNames=["linux_build", "win32_build",
>                                           "macosx_build"])I
> sign_scheduler = Scheduler(name="sign", branch="sign",
>                            treeStableTimer=0,
>                            builderNames=["sign"])
> l10nverify_scheduler = Scheduler(name="l10verify", branch="build",
>                             treeStableTimer=0,
>                             builderNames=["macosx_build"])
> update_scheduler = Scheduler(name="update", branch="update",
>                              treeStableTimer=0, builderNames=["update"])
> stage_scheduler = Scheduler(name="stage", branch="stage",
>                             treeStableTimer=0, builderNames=["stage"])
>
> ####### DEPENDENT SCHEDULERS
> build_depscheduler = Dependent(name="build_dep", upstream=tag_scheduler,
>                                builderNames=["source", "linux_build",
>
> "macosx_build", "win32_build"])
> sign_depscheduler = Dependent(name="sign_dep", upstream=build_scheduler,
>                                 builderNames=["sign"])
> update_depscheduler = Dependent(name="update_dep", upstream=sign_scheduler,
>                                 builderNames=["l10nverify", "update"])
> stage_depscheduler = Dependent(name="stage_dep", upstream=update_scheduler,
>
> builderNames=["linux_update_verify",
>
> "win32_update_verify",
>
> "macosx_update_verify",
>                                              "stage"])
>
> c['schedulers'].append(tag_scheduler)
> c['schedulers'].append(build_scheduler)
> c['schedulers'].append(update_scheduler)
> c['schedulers'].append(stage_scheduler)
> c['schedulers'].append(build_depscheduler)
> c['schedulers'].append(sign_depscheduler)
> c['schedulers'].append(update_depscheduler)
> c['schedulers'].append(stage_depscheduler)
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>
>




More information about the devel mailing list