The Jenkins community discusses various project-related topics in multiple channels on the Freenode IRC network.

For information on how to connect, see the Freenode website.



This is the primary channel for discussions about Jenkins. In you have questions about Jenkins, you’ll probably want to ask them here.

if you have a question about Jenkins, just ask it — don’t ask whether you can ask a question. It’s common to not receive an answer for quite a while if no active contributors are currently checking IRC. In that case, just stick around, and periodically (every few hours) ask your question again.

Conversations in this channel are automatically archived to both echelog and

We use the jenkins-admin bot to automate common administrative operations. Its use is limited to users with voice or op in this channel. Learn more.

Board members and officers typically have op (@) in this channel. Established contributors typically have voice (+) in this channel.


The channel to help organize events, documentation and more "meta conversations" around the Jenkins project. We don’t discuss Jenkins — the software — here.


We conduct bi-weekly project meetings in this channel. These meetings are open to everyone. [Learn more about the project governance meeting.

Meetings are logged, and the channel is unused the rest of the time. We use the robobutler to run these meetings. See the about project meetings for more details.


Discussions of the Jenkins project infrastructure, i.e. most services running on,, and related domains.


Invitation-only IRC channel for the Jenkins security team.


Commit messages of commits pushed to GitHub will be posted here by github-jenkins. Note that this channel may be empty most of the time, but messages still are posted.


#jenkins is not only a registered channel, but the Jenkins project has an official relationship with Freenode (see the Freenode site for more details). Because of this, we can provide IRC cloaks for developers. IRC cloaks are used to protect the privacy of developers. Cloaking is also a common way for projects with an IRC presence to designate status for contributors and developers. We currently offer the following cloak levels:

  • jenkins/developer/(username)

To obtain a cloak:

  • ensure you have a registered user on Freenode

  • ensure you are already recognized as a developer (have +vV voice privilege)

  • email with those details

  • monitor your memoserv notices for updates from Freenode staff requesting confirmation of cloak request

    • /msg memoserv help