I'm facing connection failure with some slack channels (Not with all) in Jenkins. I'm using Jenkins version 2.303.2 and Slack Notification Plugin version 2.28. I tried by updating Jenkins and installing different Slack plugin versions like 2.39, 2.40.
This is strange that I'm having issue with some random channels and working with some Private channels and some Public channels.
Here an example image with my error
Related
I want to integrate jenkins(2.157) with nexus for uploading / downloading artifacts and using Nexus Platform plugin with version 3.3.20190108-134259.b70ae43. When trying to connect to nexus repository manager(3.7) from jenkins using uname and password, its not connecting, resulting in error - Nexus Repository Manager 3.x connection failed.
Gone through similar issues in stackoverflow and jenkins support but no luck.
Expecting Test Connection should be success as a first step when connecting from jenkins.
enter image description here
How can I use Slack trigger a Jenkins build for which Jenkins is hosted in a enterprise server without Internet connectivity?
I tried slash command in Slack, but when slack is trying to reach the Jenkins URL error is returned since its not accessible in internet.
We recently rebuilt our Jenkins server and we are using Jenkins 2.3.5/JDK8/ubuntu 14.04/bitbucket cloud/hipchat cloud.
After we got the newly built Jenkins server running, everything worked except for the build result notification.
We used to get the bitbucket account that we used with Jenkins to comment on the build result, so we can receive it in the hipchat room, even without using hipchat notification plugin. Now, we have tried the emailext plugin, Bitbucket Build Status Notifier Plugin, but none of them worked. It seems that the plugin is all out of date in terms of configurations.
For emailext, it complains "An attempt to send an e-mail to empty list of recipients, ignored." But we put a number of email in the "Default Recipients". And all the SMTP settings are correct since we can receive testing message.
For Bitbucket Build Status Notifier Plugin, I followed here, but I couldn't find the "Bitbucket notify build status" in the job configure.
Any suggestions would be appreciated.
Use Extended Email notification plugin, set SMTP server in Jenkins global configuration
how do I configure slack and jenkins -
to get jenkins build statuses (with link to build) into specific slack room,
automatically after build is finish ?
found an answer to my question in slack site,
after installing jenkins plugin in slack
(from : https://hubot-nga.slack.com/apps)
I got detailed instructions + unique team-domain and integration token.
in addition all the required steps to complete the integration in jenkins.
I'm trying to add the HipChat plugin to my Jenkins builds, but it doesn't post anything.
In the global configuration I've set the HipChat server to api.hipchat.com, added an API token und default room ID, set the build server URL to https://xxx.ci.cloudbees.com/ and the send as name to Jenkins.
In the build job configuration I've tried setting the same room ID and leaving the field blank (so it should use the default). I've activated all notify checkboxes and added HipChat Notifications as the (only) post-build action.
However, I'm not receiving any build updates in the given room. So I've added a custom Jenkins logger, logging ALL from jenkins.plugins.hipchat. For every build I start, I get a single log entry like this:
Aug 28, 2014 6:08:20 PM INFO jenkins.plugins.hipchat.HipChatNotifier$HipChatJobProperty prebuild
Invoking Started...
Any ideas what I'm doing wrong or how I could debug this further?
PS: I'm running on Cloudbees — not sure if this makes any difference.
The Hipchat notifier plugin for Jenkins uses the HipChat API v1, not the newer API v2. I had the same problem while trying to use a v2 token.
Try creating an admin token in Hipchat for Jenkins (e.g., https://my-hipchat-group.hipchat.com/admin/api) instead of creating a room token (e.g., https://my-hipchat-group.hipchat.com/admin/rooms/tokens/665113).
I was able to get the HipChat API v2 token working with a manually built hpi from the https://github.com/yagince/hipchat-notifier-plugin project.
This seems to have been addressed in the 0.1.9 and newer versions of the hipchat plugin at https://wiki.jenkins-ci.org/display/JENKINS/HipChat+Plugin. I'm using it with a v2 API token.