[10:28] -NickServ- my_nickname is not a registered nickname.
[10:28] == #jenkins Cannot join channel (+r) - you need to be identified with services
The Jenkins project meets to discuss various topics on Gitter and IRC. In addition to the general purpose rooms and channels listed below, special interest groups and sub-projects have their own spaces, and you will see chat rooms linked from their pages.
The Jenkins community discusses various topics in multiple rooms on Gitter. Various special interest groups also use Gitter to meet, and you will find their rooms linked on the SIGs overview page.
General discussions about Jenkins.
Q&A channel for newcomer contributors to Jenkins. Use this channel if you are not sure where to ask, and other contributors will help you. More about contributing to Jenkins.
The Jenkins community discusses various project-related topics in multiple channels on the Libera Chat IRC network.
For information on how to connect, see the Libera Chat website. Find an IRC client.
#jenkins
General discussions channel for Jenkins users and developers. It used to be the primary one until non-IRC communication options were introduced. Board members and officers typically have op (@) in this channel. Established contributors typically have voice (+) in this channel.
Tip: 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.
#jenkins-infra
Discussions of the Jenkins project infrastructure, i.e. most services running on jenkins.io
, jenkins-ci.org
, and related domains.
#jenkins-hosting
Chat of the Jenkins Hosting team that manages permissions and handles plugin hosting requests. 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 about the IRC Bot.
Because of irregular spam attacks, we sometimes have to make some channels protected. In such circumstances, we make the targetted channel(s) only accessible to registered IRC nicks. Example error:
[10:28] -NickServ- my_nickname is not a registered nickname.
[10:28] == #jenkins Cannot join channel (+r) - you need to be identified with services
That means you basically need to create a reserved nick for you, following the official documentation.
Once done, you will be able to connect to #jenkins
even if that channel is undergoing a spam attack.
Note that even without this, this is a recommended practice so that people know this is you, and cannot be someone else, when a given nick is online.
#jenkins is not only a registered channel, but the Jenkins project has an official relationship with Libera Chat (see the Libera Chat 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/contributor/(username)
To obtain a cloak:
ensure you have a registered user on Libera Chat
ensure you are already recognized as a developer (have +vV voice privilege)
Contact a Jenkins Infrastructure Team member, who will request a cloak on your behalf in #libera-community
monitor your memoserv notices for updates from Libera Chat staff requesting confirmation of cloak request
/msg memoserv help
Some teams and working groups use Slack for communications.
Continuous Delivery Foundation (CDF) Slack is used for coordinating the Jenkins community activities with the CDF, other projects and special interest groups. Any contributor can join this channel, but the Jenkins community does not currently host its official channels there. Join CDF Slack
The Kubernetes Slack includes an unofficial #jenkins-ci
channel.
This channel is commonly used to discuss various aspects of running Jenkins in Kubernetes.
Our sister project Jenkins X also hosts its official chats there (links).
You can join this Slack workspace by requesting an invitation here.
The Jenkins Operator sub-project uses a separate #jenkins-operator
channel on virtuslab-oss.slack.com.
See more information and joining guidelines here.