Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

Hot answers tagged


As far as I was able to tell it's not possible. We solved this by using Pipeline putting the custom messages in the Jenkinsfile. The flexibility gained by having the Jenkinsfile in the git repo really helped our developers have a better understanding of the build process, and allowed them to make necessary changes to the build commands without the ...


In Groovy you have to use double quotes to get string interpolation: if ( "$output" != null ) { slackSend (channel: "@${name}", color: '#36A64F', message: "Job succeeded") } else { slackSend (channel: "@${name}", color: '#36A64F', message: "Job failed") } You can also probably do something like this to avoid it entirely and have ...


The plugin you found doesn't have a 1:1 ratio between Heroku instance with build jobs since it takes the job name as parameter, so you should be able to run any number of jobs from a single Heroku instance. As for passing a space in a job parameter, the word split is made on spaces so quoting won't change anything. You could possibly try to use the HTML ...


ChatOps uses GitHub status checks, so it's decidedly GitHub specific and won't work with another provider. However, if you're just after notifications, what about Heroku's App webhooks? They have an 'entity' for new app releases (api:release) which might partially help you... in that you can set up a notification for successful releases, at least. ...


I figured out by myself, there is no plugin needed. &> /dev/stdout | tee jenkins.txt and then . curl -F file=@jenkins.txt -F channels=yourchannel -H "Authorization: Bearer your token" . there is no '#' needed for slack channel and channel should not be private. And if use . | tee jenkins.log ...


Based on the PagerDuty documentation on Cloudwatch, it doesn't look like it's configurable:


Posting the full stack trace tends to clog up the channel. Here are a few things you can do: Send build status along with the Jenkins Job link to the Channel so Devs can come back to the link for debugging Send stack trace as a file Send build status as and link to channel and Stack trace info to the user who committed the code for build Either way, Post ...


You probably want the console output to be posted as an attachment, not a message, to slack. The post to slack plugin might be what you are looking for. The other thing you could do is create a part of the freestyle job that strips out what you want to a text file, and add that as part of the slack message attachment, in the slack plugin configuration.


Within the CloudWatch integration in PagerDuty, you can change the "Derive name from" field to something like "Alarm Description".

Only top voted, non community-wiki answers of a minimum length are eligible