Hi Neil, > > > However, not everything is perfect. For example, I do not get a force > build button on the non-UI master's builder (nor a 'clear the queue' > button). That will drive my users crazy for sure. >
You need to configure all the force-schedulers on your UI masters. forceschedulers defined in the non-UI masters will not be used, as they have to be in the UI. This is tracked on http://trac.buildbot.net/ticket/2673 > And I'm not sure how to determine whether the masters are talking to > each other or that the UI master is just reading the database for the > other masters' information. > the masters are talking to each other via crossbar. an easy way to make sure this work is to start a build on a non-ui master, and see it auto-update in the ui-master. If you get autoupdate then the mq is correctly working. If you have to reload the UI (F5) to see build progress, then it means the ui master can only get updated data via DB, and not via message queue. You might also have a look at tcpdump on the crossbar port to see the activity to crossbar. I can see that you have an asymetric configuration for multi-master. http://docs.buildbot.net/latest/manual/concepts.html?highlight=asymmetric#multimaster I would recommend to first start with symetric configuration where all the masters have UI, and all masters have all builders/schedulers regards Pierre
_______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
