{jenkins-plugin-info:ironmq-notifier|adopt-message=The maintainer is looking for a co-maintainer.}

This plugin uses the IronMQ messaging service to send status updates of build information into an enterprise level cloud based message queue.

Caution - Messages added into queues are not set to remain there forever and expire !!

  • Messages are not intended to be in this queue for long-term storage.
  • Default expiry if not provided is 604,800 (7 days).

The messages have FIFO (first-in first-out) ordering so ensure continuity and can be dealt with by different clients as needed.

The current build status is :   

1.0.18 - will use a minimum version of 2.7.2 version of jenkins, tested to 2.29

1.0.17 - test and set to allow install on 1.651.3 version of jenkins

1.0.16 - Initial pre-release v2 pipeline

1.0.15-Not released - Deployment issues

1.0.14 - tested with 1.651.2 LTS

1.0.13 - nothing special

WARNING: You will need to change the hosts you send messages to, and the message format has changed in this release. (1.0.12 and above)

Note: 1.0.12 has major changes to support for the new Version 3 ironmq api. The version 2 api has been deprecated by Iron.io.

One of the biggest change in the new ironmq API is the removal of the ability to put expiry seconds on individual messages to a queue.

The following change will occur from version 1.0.12 forward.

Note: 1.0.11 - enhancement - defaults settings simplify adding post-build actions.

Setup Instructions for Iron.io

At the time of the creation of this document, no setup or accounts are needed at Rackspace or Amazon. It is all handled nicely through the one interface at Iron.io

Sample Jenkins Project (not the Settings Icon) which will provide authentication token for your Project (Jenkins in this example).

You will need the following information:

Current options for Server Names are..

Starting from version 1.0.11, configure default settings in the Configure Jenkins Server Defaults as follows;

These settings will be used by default when adding a Post-Build action to new jobs.

After downloading the plugin into your Jenkins server, when creating a job, go to Post-Build Action and add a Step called "Send message to IronMQ".

You will then see the following options. (please note, these are not valid #s and are for presentation only).

The next time your build executes, it will send the results to your ironMQ mesasge queue.

As of Version 1.0.5, when a message is transmitted to the queue, it is in JSON format to allow for applications to be created with intelligence based on the data in the Queue.

Current To-Do list

Change Log

Version 1.0.13 (Dec 16, 2015)

Version 1.0.12 (Dec 9, 2015)

Version 1.0.11 (Oct 16, 2015)

Version 1.0.10 (Mar 27, 2015)

Version 1.0.6 (Oct 21, 2013)

Version 1.0.5 (Oct 8, 2013)

Version 1.0.4 (Oct 7, 2013)

Version 1.0.3 (Oct 5, 2013)

Version 1.0.2 (Oct 3, 2013) (minimum recommended version)

Version 1.0.1 (Oct 3, 2013)

Version 1.0 (Oct 2, 2013)