Hi everyone,
Thanks for the advice previously. It's helped a lot. I'll be restarting
our master tomorrow with bits of new code. In particular the new log
code, a UI fix that came from rc2 (and ended up with the benefit of the
cancel queue button, unfortunately useful in our case), and a fix for
exceptions we were getting during reconfig (a problem with __cmp()__ in
ComparableMixin. I never hunted it down -- it may have been things we
were attaching to various items. The error was that cmp() couldn't
handle sets. We're currently using that code on a second master, and we
don't except when we reconfig using the same master.cfg.
I've been getting ready to attempt using multi-master, and I ran across
possibly conflicting documentation.
Here
(http://docs.buildbot.net/latest/manual/cfg-global.html#multi-master-mode),
it says,
"Ensure that each named scheduler runs on only one master. If the same
scheduler runs on multiple masters, it will trigger duplicate builds and
may produce other undesirable behaviors."
Here
(http://docs.buildbot.net/latest/manual/cfg-schedulers.html#scheduler-resiliency),
it says:
"In a multi-master configuration, schedulers with the same name can be
configured on multiple masters."
If these aren't contradictory, where is my understanding failing?
Alternately, if they are conflicting, which is correct? Or is there
another answer?
It would also appear that some other documentation needs some updating.
Here
(http://docs.buildbot.net/latest/manual/cfg-global.html#database-specification),
the first database specification given matches closely with what
buildbot create-master produces, c['db'] = { 'db_url' : "",}
The rest use a form likec['db_url'] = "sqlite:///state.sqlite.
My guess is that the second is an older form? I could be wrong, never
having tested the other form.
I've been able to get 2 masters talking to the same database (postgres
in our case), but I'm still working on getting all the changes that need
to be made down pat before using our own master.cfg. That's just me
getting up to speed.
We like the cancel queue button, even though we got it accidentally. It
came in with a change we needed to the builders page. We needed to be
able to see the results of the last build regardless of when it built.
Since the source for the pages isn't in the regular source tarball, the
guy who did the change used the rc2 version, and we got a new feature we
liked for free. On the other hand, people seem to have liked the old
waterfall better.
Thanks again for your time.
Neil Gilmore
grammatech.com
_______________________________________________
users mailing list
users@buildbot.net
https://lists.buildbot.net/mailman/listinfo/users
