Opened on 02/26/2016 at 04:49:37 PM

Last modified on 12/04/2017 at 11:19:53 AM

#3708 new change

Have abpbot join all channels

Reported by: kzar Assignee: matze
Priority: Unknown Milestone:
Module: Infrastructure Keywords: abpbot, irc
Cc: fhd, kvas Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by trev)


We have an IRC bot that currently resides in #adblockplus. During recent changes Felix noticed a few things that need changing with it...

What to change

  • Have it join all of our IRC channels, not just #adblockplus on
  • Ensure something sensible is happening with the created logs. (I'm not exactly sure about what that is.)
  • Rename the bot to abpbot from abplogbot as it now does more than just logging.

Attachments (0)

Change History (6)

comment:1 Changed on 02/26/2016 at 04:50:17 PM by kzar

Note: I'm filing this on Felix's behalf, I might have omitted something or got some of the details wrong.

comment:2 Changed on 02/26/2016 at 04:51:02 PM by kzar

  • Summary changed from Move abpbot onto it's own server, have it join all channels to Move abpbot onto its own server, have it join all channels

comment:3 Changed on 02/26/2016 at 05:00:25 PM by fhd

Well I suppose these should be separate issues :D But I guess this'll do for now, once someone finds time to work on any these they can write more issues.

comment:4 Changed on 06/07/2016 at 02:47:34 PM by matze

In the context of #4103 we've now made abpbot run on a separate host (forgot about the existence of this ticket here when that one was created a few days ago). In the context of #4104 we still need to follow-up on this, properly integrating the setup with Puppet.

Afterwards we can finally tackle #308, in which context log publication has been requested quite a while ago already (blocked so far by the setup not being included with our configuration management, monitoring etc. in the first place).

Automated re-provisioning or updates based on patches in the repository are a no-go*. At least until we have established proper CI for the entire development cycle, and in that context we will need some more IRC logging, for all of which the abpbot is far from suitable anyway. So I doubt that this will ever happen, it's way more likely that we revamp that thingy from the core up. These considerations also render renaming overhead for now.

*) I realize that this is done in some parts of our system, but we have already established that we need to overhaul these resources / processes as well.

comment:5 Changed on 06/07/2016 at 02:51:15 PM by matze

  • Cc kvas added; matze removed
  • Owner set to matze

comment:6 Changed on 12/04/2017 at 11:19:53 AM by trev

  • Description modified (diff)
  • Summary changed from Move abpbot onto its own server, have it join all channels to Have abpbot join all channels

I removed the points covered by #4103 and #4104.

Add Comment

Modify Ticket

Change Properties
as new .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from matze.
Next status will be 'reviewing'.
Note: See TracTickets for help on using tickets.