jenkinsci / slack-plugin Goto Github PK
View Code? Open in Web Editor NEWA Jenkins plugin for posting notifications to a Slack channel
Home Page: https://plugins.jenkins.io/slack/
License: MIT License
A Jenkins plugin for posting notifications to a Slack channel
Home Page: https://plugins.jenkins.io/slack/
License: MIT License
When working with condition job step, totally fubarrs ... stack trace to follow.
If I include the built-in email notification plugin and the Slack plugin in my project, I don't get Slack notifications.
Two (probably the first I've configured) jobs keep pushing notifications, but others seem to just not trigger the plugin at all. Here is how I now configured the "FFFFFFFF" job, that successfully pushes notification, and the "slack_test" job in configured in the same way.
Both of them have exit 1
in shell script to be executed, but only the "FFFFFFFF" job pushed notification.
мар 17, 2015 6:13:40 PM INFO hudson.model.Run execute
FFFFFFFF_Selenium_Tests #45 main build action completed: FAILURE
мар 17, 2015 6:13:40 PM INFO jenkins.plugins.slack.StandardSlackService publish
Posting: to #jenkins-ci on ******** using https://********.slack.com/services/hooks/jenkins-ci?token=********: FFFFFFFF_Selenium_Tests - #45 Failure after 0,12 секунд (<https://********/job/FFFFFFFF_Selenium_Tests/45/|Open>) danger
мар 17, 2015 6:13:40 PM INFO jenkins.plugins.slack.StandardSlackService publish
Posting succeeded
мар 17, 2015 6:23:56 PM INFO hudson.model.Run execute
slack_test #3 main build action completed: FAILURE
If I update the global configuration of the slack-plugin, say the API key, then the slack configuration that exists in current jobs isn't updated.
I basically had to do a massive search replace to get around this. It would be nice if I didn't have to remove and add the slack post commit task to each job just to change global config.
work arounds:
find . -name 'config.xml' -exec sed -i 's/<teamDomain>mydomain.com<\/teamDomain>/<teamDomain>mydomain<\/teamDomain>/g' "{}" \;
find . -name 'config.xml' -exec sed -i 's,<authToken>1234578901234567u693453</authToken>,<authToken>11111111111111111111111</authToken>,g' "{}" \;
Have a lot of these in my log after upgrade to 1.560.
Apr 22, 2014 8:26:38 AM hudson.model.listeners.RunListener report
WARNING: RunListener failed
java.lang.NullPointerException
at jenkins.plugins.slack.ActiveNotifier.completed(ActiveNotifier.java:65)
at jenkins.plugins.slack.SlackListener.onCompleted(SlackListener.java:26)
at jenkins.plugins.slack.SlackListener.onCompleted(SlackListener.java:14)
at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199)
at hudson.model.Run.execute(Run.java:1753)
at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
We use the CloudBees Folders Plugin a lot. Folders typically contain a project named 'build'. At present notifications don't include the full project name so can be ambiguous.
Instead of using a custom 'Build Server URL' parameter, we can't use the built in 'Jenkins URL'(Manage Jenkins > Jenkins Location)?
related #3
For e-mail notifications, you can tell Jenkins to only notify the person who broke the build. It would be handy to have the same for the Slack notifications.
We've got Jenkins setup to deploy to a "dev" lane when an option boolean is checked. It'd be nice if we could set notifications to only happen when that checkbox is toggled.
This is a request to Jenkins Slack Plugin contributors to create jelly documentation for the plugin options. I believe this would improve the overall user experience if some or all options included a help doc explaining what that option does.
The expected behavior is to be able to click the help button next to the option. Here's a screen shot showing an example.
All contributions welcome. If you would like to be invited to the Jenkins plugin slack then let me know. That slack org is meant to assist contributors with testing changes.
It was 3 months since color-coding was merged and still from jenkins dashboard only the old version is available.
I get this error in my Jenkins log whenever the plugin attempts to send a message to Slack:
Slack post may have failed. Response: Invalid channel specified
I've followed the steps in the setup page and believe everything is as it should be. Team domain and token are set, channel name is blank (tried using 'builds' and '#builds' as well), build server URL is /
Jan 13, 2015 10:34:44 AM WARNING jenkins.plugins.slack.StandardSlackService publish
Slack post may have failed. Response: Invalid channel specified
Not sure if this is a Slack problem or a plugin problem.
In Jenkins "Configure System" I've setup appropriate slack settings. Test Connection returns SUCCESS, although on further testing that seems to be the case no matter what nonsense I enter.
Some jobs are also configured to use the Slack Notifier but when running the console log has no mention of slack and slack is not notified.
How am I supposed to debug what's going on so that I can diagnose and resolve the problem?
Jenkins 1.580.3 + Slack Notifier 1.7.
We have some jobs that run on a timed schedule. If they fail, we get notifications each time. So our #jenkins channel fills up with lots of fail messages.
It would be nice to have an option like “Notify First Failure”. That way we could get notified (once!) when the job fails, and once when the job is back to normal, using the “Notify Back To Normal” option.
When configuring the Slack integration, you can select particular users instead of channels. But this option is not anywhere in the Jenkins plugin configuration. Is it supported at all? If so, how is it used?
I've tried <username>
& @<username>
on the Project Channel setting but none of them worked (ie. no messages at all posted).
I have a a job that is using the build flow plugin to run several jobs in parallel. While aborts and build complete notifications are sent, the initial job started notification never is sent to slack, it appears. All the child jobs send notifications that they were started by the build flow job.
Slack allows the attachments parameter to set a colored left-hand border for each message. CI systems like Travis use this border to indicate the status of the build:
Please support this when Jenkins posts to Slack.
Jenkins generate some outputs for each build, which is shown in "Console output" panel for each build.
Can I make the slack-plugin post that output to slack? Is this feature already available?
I tried checking the box " Include Test Summary" in the slack notification configuration. However, what I got on slack is "No Tests found."
When using with Flexible publish plugin it fails.
https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin
The plugin should implement SimpleBuildStep
to allow being called from the workflow-plugin https://github.com/jenkinsci/workflow-plugin
I installed the Slack integration plugin 1.2 on a Jenkins server (v1.555, have also tried on 1.566 with same result). Followed all relevant instructions for installation and configuration, but the plugin is either not functioning or its updates are not being posted by our Slack instance.
To troubleshoot I boosted the Jenkins log levels to 'all', but the Slack plugin appears to have no logging whatsoever which could help me to deduce what the root cause could be. I have successfully installed a Slack plugin on another one of our Jenkins servers and it's posting without any problems.
There is no documentation about how to use this?
Including the branch name in the slack notifications.
Also, not sure how to provide better customization of the slack notifications.
Contributions are welcome.
Jenkins: 1.549
Java: 1.7.0_51-b13
OS: OSX 10.7.5
Slack plugin: 1.2
Changing the buildServerUrl in my Jenkins config was not having any effect: all build notifications in Slack still referred to the URL that I entered when I first configured the plugin.
I realized that this is because, while jenkins.plugins.slack.SlackNotifier.xml
was being updated properly, my job-specific config was not.
However, there is no field in the project configuration frontend to set the buildServerUrl parameter.
Removing and re-adding the "Slack Notifications" post-build action resolved the issue for me, in the end.
I was just curious if there's any interest (aside from just me) in adding some way to modify the instance variables inside SlackNotifier.DescriptorImpl?
https://github.com/jenkinsci/slack-plugin/blob/master/src/main/java/jenkins/plugins/slack/SlackNotifier.java#L81
I'm using Chef to manage my Jenkins instance, and I'd like to have Chef set the appropriate values for Slack as well. Most of these are managed via Groovy scripts submitted via the jenkins-cli.jar. Unfortunately, it looks like the only way to modify the Slack values would be by creating a RequestImpl to "fake out" the form submission. That's not really too desirable. Instead, this could be resolved by adding setters for those values (or some other method to modify them) similar to the mailer-plugin: https://github.com/jenkinsci/mailer-plugin/blob/master/src/main/java/hudson/tasks/Mailer.java#L201
I'd be happy to do this work and issue a pull request if there's any interest. Thoughts?
We configure Jenkins to build any git branch pushed to our review repository. It would be nice to see the branch name in the build notification through the use of format specifiers. At the moment, you need to click through to see what job actually finished.
The info/tooltip of team domain/token on the job configuration page mentions that it inherits the values from global. This doesn't appear to be case. With empty fields (except for channel) the test says "success" but no messages are delivered.
After filling in the domain and token it does properly send the message.
I installed your plugin and it seems to do nothing. There are no logs generated on my jenkins box. Is there a way to turn on logging for this plugin, so I can debug the problem?
We have a bunch of private groups where we would like to send Jenkins notifications.
Right now pushing a message to a private group gives:
Aug 04, 2014 1:10:55 AM jenkins.plugins.slack.StandardSlackService publish
WARNING: Slack post may have failed. Response: No active hooks
"Failed to initialize campfire notifier - check your global campfire notifier configuration settings: javax.net.ssl.SSLProtocolException: Server returned wrong cipher suite for session"
See related info here -> https://issues.jenkins-ci.org/browse/JENKINS-19590
Essentially, the plugin installs fine, but when I go to set up the org name and key in "Configure System", I get the error above.
I'm currently having issues releasing the plugin. Here's an excerpt from slack...
21:01 < sag47> kohsuke: I'm having trouble releasing a plugin. My GitHub username is samrocketman and my jenkins-ci.org ID is sag47. I have added my credentials to ~/.m2/settings.xml from this article
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
21:02 < sag47> kohsuke: Do I have the capability to release if I'm able to be a contributor for a plugin? If not, what do I need to do in order to be able to release?
21:02 < sag47> kohsuke: I have taken over maintaining this as it was previously abandoned.
21:03 < sag47> kohsuke: Plugin in question: https://github.com/jenkinsci/slack-plugin
I'll be working through this and keep any followers for the next release updated via this issue.
The first time I used the Jenkins Slack plugin, I experienced trouble finding the right syntax for configuring a job to notify multiple Slack channels. In the future, could we increase flexibility?
#chan1,#chan2,...
)#chan1 #chan2 ...
)#chan1, #chan2, ...
)It would be nice if the notifications included:
I've seen several Jenkins plugins with a "Test Connection" button. See the Gerrit Trigger for an example.
That would definitely be useful in this plugin to make sure you have the correct settings. I was trying to set this up and apparently specified an invalid channel. It took me a while to figure that out, since it is only in the system log, not the build log.
Slack Plugin simply inserts its configuration options somewhere in the middle of the top section of the Jenkins Configure page.
There is no visible separator at the end of its section, making it quite difficult to find out which options belong to the plugin and which don't.
Currently, I accept pull requests with no unit testing. It would be good if more unit tests were written to exercise the code base. It would certainly make me more confident when merging contributions. Although I do, and will continue to, manually test the plugin when merging. It is generally accepted as a software development best practice.
For those who don't know me, I don't actively develop this plugin. I do maintain pull requests and releases.
We are using Ivy for dependency management. This results in there being module builds for each jenkins project. For some reason build failures aren't going to slack. Only "back to normal" messages are being sent there.
In Jenkins Manage configuration , set global values for Slack; however, when going in to a Job that uses Slack, hitting the "Test Connection" is says "Success" BUT the Jenkins logs show:
Feb 23, 2015 10:03:17 PM INFO jenkins.plugins.slack.StandardSlackService publish
Posting: to on using https://.slack.com/services/hooks/jenkins-ci?token=: Slack/Jenkins plugin: you're all set. green
Feb 23, 2015 10:03:17 PM WARNING jenkins.plugins.slack.StandardSlackService publish
Error posting to Slack
java.net.UnknownHostException: .slack.com
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618)
at sun.security.ssl.SSLSocketImpl.<init>(SSLSocketImpl.java:451)
at sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:140)
at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:82)
at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:127)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at jenkins.plugins.slack.StandardSlackService.publish(StandardSlackService.java:66)
at jenkins.plugins.slack.SlackNotifier$SlackJobProperty$DescriptorImpl.doTestConnection(SlackNotifier.java:358)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46)
at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103)
at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:370)
at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960)
at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Feb 23, 2015 10:03:17 PM INFO jenkins.plugins.slack.StandardSlackService publish
Posting succeeded
On latest 1.7 release
Hi,
We are seeing the occaionaly Null Pointer Execption from the Jenkins Slack Notification plugin:
"
FATAL: null
java.lang.NullPointerException
at java.util.AbstractCollection.addAll(Unknown Source)
at jenkins.plugins.slack.ActiveNotifier.getChanges(ActiveNotifier.java:115)
at jenkins.plugins.slack.ActiveNotifier.started(ActiveNotifier.java:45)
at jenkins.plugins.slack.SlackNotifier$SlackJobProperty.prebuild(SlackNotifier.java:280)
at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:804)
at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:799)
at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:795)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:530)
at hudson.model.Run.execute(Run.java:1745)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
"
Slack Notification Plugin 1.7
It would be cool to allow for customizing the message a bit. Specifically I'd like to include the branch name. But maybe there are other tokens people would include or exclude.
There is a really great plugin that allows you to build an inheritance tree for your builds, but this notification plugin just doesn't work with it.
I don't know the specific requirements for getting plugins to work with the inheritance plugin but I wanted to open this issue and cross post an issue from their repo to get a conversation started.
Here is the repo for the plugin: https://github.com/i-m-c/jenkins-inheritance-plugin/
It would be great to enable admins to set the bot name (and its icon) in post-build action preferences.
These parameters could be send in each message payload using username
and icon_url
fields.
Add a field for a custom message, such as "A new version of X is now available."
Hi,
we have one Jenkins instance and multiple Slack teams (projects). Current plugin in global settings defines Slack "secrets" so you can't configure it for multiple teams.
So either put this to the build configuration or enable definition of Teams in th global settings where a value can be than picked for a specific build.
This is quite a showstopper for our case.
Can I expect the fix in a reasonable time or do we have to make a change ourselves?
thanks in advance
Peter
Hi,
I did everything the guideline says to make this work. But it's not working.
I have a http proxy on my environment.. do you guys know or someone has already tested it behind a proxy?
My logs says:
Apr 16, 2014 1:42:41 PM INFO jenkins.plugins.slack.StandardSlackService publish
Posting: to on walmartbr using https://xyz.slack.com/services/hooks/jenkins-ci?token=[TOKEN]: python_scripts-code_pull_test_build - #84 Success after 2 sec (</job/python_scripts-code_pull_test_build/84/|Open>) green
Apr 16, 2014 1:42:56 PM INFO jenkins.plugins.slack.StandardSlackService publish
Posting: to on walmartbr using https://xyz.slack.com/services/hooks/jenkins-ci?token=[TOKEN]: python_scripts-deploy-dev - #125 Success after 1.3 sec (</job/python_scripts-deploy-dev/125/|Open>) green
I have "Notify Back To Normal" enabled.
I had a build that was failing. I started a new build in jenkins and then cancelled the build while it was in progress.
I then tweaked the build configuration in jenkins.
I did a new build and it succeeded. I received no slack notification that the build had gone from broken to working. I suspect that's because the last build had been cancelled.
As a Jenkins newbie, I want the Slack plugin to automatically setup any post-build steps for me. I don't want to have to explicitly add a Slack post-build step to every job I manage, and I keep forgetting to do this.
Steps to reproduce:
Slack Notification Plugin 1.7
Jenkins ver. 1.600
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.