Add support for noSquash (no-squash) in jms-messaging trigger

It's sometimes required to trigger a job build on every CI message.
To achieve that the XML's noSquash (jjb: no-squash) has to be set to
True.

see triggers section at:
https://wiki.jenkins.io/display/JENKINS/JMS+Messaging+Plugin

Change-Id: I389e59cca4f649379614f7f6247bf76cf4a0ba95

1 files changed, 7 insertions, 0 deletions

diff --git a/jenkins_jobs/modules/triggers.py b/jenkins_jobs/modules/triggers.py
index 21d9a7a3..c8b6b715 100644
--- a/jenkins_jobs/modules/triggers.py
+++ b/jenkins_jobs/modules/triggers.py
@@ -933,6 +933,12 @@ def jms_messaging(registry, xml_parent, data):
     Requires the Jenkins :jenkins-wiki:`JMS Messaging Plugin
     <JMS+Messaging+Plugin>`.
 
+    :arg bool no-squash: true = schedule a new job for every triggering message.
+        (default false)
+        Normally if a job is queued and another triggering message is received, a new job
+        is not submitted and the job is "squashed" into the job already queued.
+        Setting this option to 'True' forces a new job to be submitted for every triggering
+        message that is received.
     :arg str override-topic: If you need to override the default topic.
         (default '')
     :arg str selector: The JSON or YAML formatted text that conforms to
@@ -968,6 +974,7 @@ def jms_messaging(registry, xml_parent, data):
     mapping = [
         # option, xml name, default value
         ("spec", "spec", ""),
+        ("no-squash", "noSquash", False),
         ("selector", "selector", ""),
         ("provider-name", "providerName", ""),
     ]