[Buildbot-devel] Manual Scheduler trigger?
felix at compsoc.nuigalway.ie
Wed Feb 4 17:14:18 UTC 2009
On Wed, Feb 04, 2009 at 10:46:45AM -0500, Stephen Milner wrote:
> Hey Ian,
> The way I had set this up was having 1 master (with 1 irc bot) to 1 group. So ...
> Master A
> - SlaveBuild A1 \
> - SlaveBuild A2 |--------> #chanA
> - SlaveBuild A3 /
> Master B
> - SlaveBuild B1 \
> - SlaveBuild B2 |--------> #chanB
> and so on..
> I'm sure there are other ways to make this setup, but that is how I did it :-).
> ----- Original Message -----
> From: "Ian Peters-Campbell" <mahatmamanic at gmail.com>
> To: "Stephen Milner" <smilner at redhat.com>
> Cc: Buildbot-devel at lists.sourceforge.net
> Sent: Tuesday, February 3, 2009 4:12:49 PM GMT -05:00 US/Canada Eastern
> Subject: Re: [Buildbot-devel] Manual Scheduler trigger?
> Following your advice I've set up IRC on the buildserver (handy since the company wanted an internal IRC network anyhow.) I'm ready to start instantiating some IRC Bots, but I'm not seeing an easy way to limit the builders each IRC bot has access to.
> To clarify, what I would like to do is have a separate channel for each project/dev team here at the office, and have a bot capable of performing all of the builds for that specific project reside in the channel. The channel could then be locked to ensure that only team members could fire off builds, and the build results would alwas be listed in the appropriate channel.
> Is there an easy way through existing code to create bots with a subset of builders that would allow this, or will I need to extend the bot functionality to get that behavior?
Use of categories should take care of this. Group your builds into
categories and create different IRC bot for each of the categories,
either on the same channel or different channels.
"Nothing is foolproof to a sufficiently talented fool."
More information about the devel