Amazon SNS Notifier

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID snsnotify Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
1.8-RELEASE (archives)
Oct 13, 2014
1.565.1
Source Code
Issue Tracking
Maintainer(s)
GitHub
Open Issues
Michael Watt (id: mikewatt)
Julian Kelabora (id: jkelabora)
Niko Schmuck (id: nikos)
Usage Installations 2014-Apr 184
2014-May 183
2014-Jun 195
2014-Jul 205
2014-Aug 213
2014-Sep 211
2014-Oct 211
2014-Nov 223
2014-Dec 239
2015-Jan 241
2015-Feb 242
2015-Mar 273

Send build notifications to an AWS SNS Topic.

From version 1.7 on you can customize the SNS subject and payload message making use of build and environment variables.

From version 1.8 you can set in the global configuration whether you want also to send out an SNS notification on build start.

Labels

plugin-notifier plugin-notifier Delete
amazon amazon Delete
notification notification Delete
sns sns Delete
build-status build-status Delete
plugin-post-build plugin-post-build Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jul 24, 2014

    lancenorskog says:

    My install of this does not send SNS notifications. Instead, I see this in the l...

    My install of this does not send SNS notifications. Instead, I see this in the logs after the build finishes. Note the times between the three log lines. Do I need a special port open?

    Jul 24, 2014 3:30:56 AM hudson.model.Run execute
    INFO: apixio-common #687 main build action completed: SUCCESS
    Jul 24, 2014 3:31:25 AM com.cloudbees.jenkins.GitHubRepositoryName create
    WARNING: Could not match URL git@github.com:/Apixio/common
    Jul 24, 2014 3:33:07 AM org.eclipse.jetty.util.log.JavaUtilLog warn
    WARNING:
    java.nio.channels.ClosedChannelException
        at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:265)
        at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:474)
        at org.eclipse.jetty.io.nio.ChannelEndPoint.flush(ChannelEndPoint.java:293)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.flush(SelectChannelEndPoint.java:402)
        at org.eclipse.jetty.io.nio.SslConnection.process(SslConnection.java:337)
        at org.eclipse.jetty.io.nio.SslConnection.access$900(SslConnection.java:48)
        at org.eclipse.jetty.io.nio.SslConnection$SslEndPoint.flush(SslConnection.java:738)
        at org.eclipse.jetty.io.nio.SslConnection$SslEndPoint.shutdownOutput(SslConnection.java:641)
        at org.eclipse.jetty.io.nio.SslConnection.onIdleExpired(SslConnection.java:260)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.onIdleExpired(SelectChannelEndPoint.java:349)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:326)
        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:744)

    1. Aug 25, 2014

      nikos says:

      From the stacktrace this doesn't look specific to the the snsnotify plugin. Anyw...

      From the stacktrace this doesn't look specific to the the snsnotify plugin. Anyways did you figure out the problem, might it be related to a URL misconfiguration issue?