Please fork and send pull requests to zulip/zulip-jenkins-plugin
This plugin sends messages and notifications of build statuses to Zulip.
It began its life as a fork of the Jenkins Campfire plugin.
The Zulip server is configured globally for the whole Jenkins instance.
Minimal configuration is:
- Zulip Url = The Url of your Zulip installation visible from Jenkins instance
- Zulip User Email = E-mail of Zulip bot that will be used to send messages to streams
- Zulip API key = The API key of bot that will be used to send messages to streams
Other attributes are optional:
-
Default Stream Name = The stream messages will be sent to by default. You can override this setting per project, but be not to leave it blank in both places or your messages will fail to send.
-
Default Topic Name = The topic messages will be sent to by default. You can override this setting per project. If you leave it blank at both places, Jenkins job name will be used as a topic instead
-
Enable Smart Notification = If enabled, successful build notification will be sent out only if one of following criteria is met:
- There was no previous build
- The current build failed
- Previous build failed
In another words, the notifications will not be sent for continuously succesful builds.
-
Jenkins URL =
⚠️ This parameter is kept just for the sake of backward compatibility.⚠️ Instead of setting this, configure Jenkins URL in "Manage Jenkins" > "Configure System" > "Jenkins Location" > "Jenkins URL"
Zulip notification is a post build action step, that posts notification about build statuses to Zulip Streams. The step allows you to configure two optional parameters:
- Stream = The stream messages will be sent to for this job. Will override default stream from global settings. Be sure not to leave it blank in both places
- Topic = The topic messages will be sent to for this job. Will override default topic from global settings. If blank in both places, job name will be used as topic.
For freestyle project, simply select a post build action from the dropdown and optionally configure destination stream and topic.
Scripted pipeline have no concept of post build actions, but you can still use the zulipNotification
step in the try/catch or preferably using the catchError
step
node {
catchError {
// ... Your build stages ...
}
zulipNotification stream: 'coolproject', topic: 'jenkins'
}
In declarative pipeline, simply use the zulipNotification
step inside your post actions
pipeline {
agent any
stages {
// ... Your build stages ...
}
post {
always {
zulipNotification()
}
}
}
Zulip send is a build step, that allows you to post arbitrary messages to Zulip stream throughout the build process. You can use this e.g. to notify Zulip that build has started or about various phases the build goes through. The step allows you to configure:
- Stream = Optional stream the message will be sent to for this job. Will override default stream from global settings. Be sure not to leave it blank in both places
- Topic = Optional topic the message will be sent to for this job. Will override default topic from global settings. If blank in both places, job name will be used as topic.
- Message = The message that will sent out. You can use build variables inside the message.
For freestyle project, simply select a build action from the dropdown and fill in desired message. Optionally configure destination stream and topic.
In scripted pipeline, simply use the zulipSend
step in any stage of the build
node {
stage('Prepare') {
zulipSend message: 'Started build #${BUILD_NUMBER} of project ${JOB_NAME}...'
// ... Perphaps SCM checkout here ...
}
// ... Other build stages ...
}
In declaretive pipeline, simply use the zulipSend
step in any stage of the build
pipeline {
agent any
stages {
stage('Prepare') {
steps {
zulipSend message: 'Started build #${BUILD_NUMBER} of project ${JOB_NAME}...'
// ... Perphaps SCM checkout here ...
}
}
// ... Other build stages ...
}
}
If you're using 1.x version of Jenkins and 1.x version of workflow job plugin (previous name for the pipeline jobs)
you will encounter exceptions like java.lang.NoSuchMethodError: No such DSL method zulipSend found among [...]
.
In that case, you will have to use the metastep instead. Simply replace:
zulipSend message: 'Test'
with
step([$class: 'HumbugSendStep', message: 'Test'])
and
zulipNotification()
with
step([$class: 'HumbugNotifier'])