-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
CentOS 5.4 x64, ircd-seven (latest), Atheme Services 7.0.x
We have an own installation of IRCd which is running the latest version of IRCd Seven with Atheme Services (more or less the same setup as on Freenode).
Jenkins Bot is able to join and authenticate properly and stays in the channel for some time. It is also correctly publishing notifications and responds to commands. But after a period of inactivity (we have no activity in channel during the night) it dies (basically the bot times out during the night at some point). And the only way for it to re-join is for us to restart Jenkins server which seems bad.
- is related to
-
JENKINS-28175 config change deadlock Jenkins when pircx.shutdown() is invoked
- Resolved
-
JENKINS-26491 Make ircbot interrupteble
- Resolved
-
JENKINS-12221 irc flood control
- Open
-
JENKINS-16875 Builds do not timeout when job hangs in post build actions
- Open