- Trigger Jenkins build upon receipt of a matching message.
- Await message in the middle of a Job
- Send message from Jenkins Job.
JMS Messaging Providers
- This plugin supports the following JMS Message Provider types
- ActiveMQ
- FedMsg
- RabbitMQ
Older versions of this plugin may not be safe to use. Please review the following warnings before using an older version:
Before the plugin may be used, you must add a JMS Messaging Provider. This will provide the ability to send and receive messages. Below is a list of currently supported JMS Message Providers:
- ActiveMQ
- FedMsg
- RabbitMQ
Example:
unclassified:
jmsProviders:
configs:
- fedMsg:
name: "Fedora messages"
hubAddr: "tcp://example.com:5678"
pubAddr: "tcp://example.com:6789"
topic: "org.fedora.bar"
- activeMq:
name: "Active MQ"
broker: "foo.com:4242"
topic: "active.mq.com"
topicProvider: "default"
useQueues: false
authenticationMethod:
simple:
username: "foo"
password: "bar" # User, encrypt secrets
- rabbitMq:
name: "Rabbit MQ"
exchange: "ex"
hostname: "rabbitmq.example.com"
portNumber: "4545"
queue: "foo.bar"
topic: "baz"
virtualHost: "rabbitvh.example.com"
authenticationMethod:
sslCertificate:
keystore: "/tmp/key"
keypwd: "keypwd" # User, encrypt secrets
truststore: "/tmp/trust"
trustpwd: "trustpwd" # User, encrypt secretsTo enable the CI trigger, go to the job configuration page and add click the check box "CI Event" under the Build Triggers section. Enabling the trigger on a job requires two additional pieces of information:
- Provider Name
- JMS Selector
In the image above, the selector contains CI_TYPE = '<message-type>'
The valid values for '<message-type>' can be found in the "Type" column in the table below:
| Message | Description | Type |
|---|---|---|
| Code quality checks done | Indicate that static analysis covering code quality is complete. | code-quality-checks-done |
| Component build done | Indicate that a component has been built. | component-build-done |
| Component functional test coverage done | Indicate that test coverage for component tests is complete. | functional-test-coverage-done |
| Custom | Indicate a custom event not covered by the other message types. | custom |
| Early performance testing done | Indicate that early automated performance testing is complete. | early-performance-testing-done |
| Early security testing done | Indicate that early automated security testing is complete. | early-security-testing-done |
| Engineering product build accepted for release testing | Indicate that engineering product build has been accepted as a release candidate. | product-accepted-for-release-testing |
| Engineering product build in staging environment | Indicate that engineering product build has been pushed to staging environment. | product-build-in-staging |
| Functional testing done | Indicate that all planned functional testing is complete. | functional-testing-done |
| Image Uploaded | Indicate that a cloud image has been uploaded | image-uploaded |
| Nonfunctional testing done | Indicate that all planned nonfunctional testing is complete. | nonfunctional-testing-done |
| Out of the box testing done | Indicate that end user testing is complete. | ootb-testing-done |
| Peer review done | Indicate that development has completed peer review of the code change. | peer-review-done |
| Product build done | Indicate that a new product build is complete. | product-build-done |
| Product test coverage done | Indicate that test coverage for functional product tests is complete. | product-test-coverage-done |
| Pull request submitted | Indicate that a code change needs to be reviewed and tested. | pull-request |
| Security checks done | Indicate that static analysis covering security issues is complete. | security-checks-done |
| Tier 0 testing done | Indicate that tier 0 (unit) testing has completed. | tier-0-testing-done |
| Tier 1 testing done | Indicate that tier 1 (component) testing is complete. | tier-1-testing-done |
| Tier 2 build validation done | Indicate that the build validation is complete. | tier-2-validation-testing-done |
| Tier 2 integration testing done | Indicate that tier 2 (functional product) automated testing is complete. | tier-2-integration-testing-done |
| Tier 3 testing done | Indicate that tier 3 testing is complete. | tier-3-testing-done |
| Unit test coverage done | Indicate that test coverage for unit tests is complete. | unit-test-coverage-done |
| Update defect status | Indicate a code change to resolve a defect has been reviewed and tested and the defect status needs to be updated. | update-defect-status |
This plugin provides a build step for publishing messages to the topic upon job completion. To add the CI Notifier build step, go to the job configuration page and select the "CI Notifier" option.
Adding the step to the job requires some additional information:
- Provider name
- Message type
- Message properties
- Message content.
The full list of message types available in the drop-down menu can be found in the Message Type table above.
This plugin provides a build step to wait for a specific message. To add the CI Subscriber build step, go to the job configuration page and select the "CI Subscriber" option.
Adding the step to the job requires some additional information:
- Provider name
- JMS Selector
- Variable
- Timeout
The build step will set an environment variable with the name from Variable with a value of the message content.
See above.
The CI trigger is available via the triggers section in a declarative pipeline:
triggers {
ciBuildTrigger(noSquash: false,
providerList: [ activeMQSubscriber(name: 'Red Hat UMB',
checks: [
[
expectedValue: '^foo.*bar$',
field: '$.msg.tag'
]
],
overrides: [topic: 'Consumer.rh-jenkins-ci-plugin.8dad9900-abcabc.VirtualTopic.eng.ci.example.durable.test.abcabc'] )
]
)
}Here is a usage example for Job DSL:
ciBuildTrigger {
providers {
providerDataEnvelope {
providerData {
activeMQSubscriber {
name("Red Hat UMB")
overrides {
def uuid = "4ba46bbc-949b-11e8-b83f-54ee754ea14c"
topic("Consumer.rh-jenkins-ci-plugin.${uuid}.VirtualTopic.eng.ci.redhat-container-image.pipeline.running")
}
// Message Checks
checks {
msgCheck {
field('$.artifact.type')
expectedValue("cvp")
}
}
}
}
}
}
noSquash(true)
}
}This plugin provides the steps when using the Jenkins Pipeline feature:
- sendCIMessage
- This is the Freestyle CI Notifier Build and Publisher step sibling.
- waitForCIMessage
- This is the Freestyle CI Subscriber Build step sibling.
Here are some examples:
node('master') {
// Send a message that CodeQualityChecksDone
def sendResult = sendCIMessage \
providerName: 'default', \
messageContent: 'some content', \
messageProperties: 'CI_STATUS = passed', \
messageType: 'CodeQualityChecksDone'
// echo sent message id and content
echo sendResult.getMessageId()
echo sendResult.getMessageContent()
}and
node('master') {
// Wait for message and store message content in variable
def msgContent = waitForCIMessage \
providerName: 'default', \
selector: "CI_TYPE = 'code-quality-checks-done' and CI_STATUS = 'passed'"
echo "msgContent = " + msgContent
}- Revert #181. Version 2.x will incorporate an improved ability to override the use of queues and topics on a job/pipeline step level.
- Correct regression introduced in 1.1.16 that caused the CI Event configuration of Pipeline jobs to appear to have been reset upon configuring the job.
WARNING: This version contains a regression involving the display of job configuration data of Pipeline jobs. Please use v1.1.17
- Correct presentation of data model for CI Notifier and CI Subscriber (#187) @scoheb
- Correct location of RabbitMQPublisherProviderData help files (#188) @scoheb
- Allow sending notification to queue when useQueues is true (#181) @ArturHarasimiuk
- remove not used context dependency on hudson.Launcher (#182) @ArturHarasimiuk
- Do not ignore Select/Choice parameters when triggering builds
- Set minimum core version to 2.150.2
- Add support for Fedora messaging wire format
- Bump jackson-databind from 2.9.10.1 to 2.9.10.3 in /plugin
- When Jenkins is restarted, customized JMS configuration is silently reverted to same (default?) values (#170)
- Fix: Incorrect timestamp format with RabbitMq (#169)
- Fix: CI_MESSAGE has incorrect format with RabiitMq (#168)
- Move ath to module to escape the dependency hell (#164)
- Add example for triggers in pipeline dsl and job dsl (#160)
- Update json-path from 2.3.0 to 2.4.0 (#129)
- Update jeromq from 0.4.0 to 0.4.3 (#128)
- Upgrade jackson-* packages (#156)
- Upgrade activemq-amqp to 5.15.9
- Add simple client for RabbitMQ (#154) (thanks @Zlopez)
- Migrate to use GitHub README for plugin documentation (#153)
- Correct handling of Boolean Parameters during triggering (#152)
- Ensure tests work (#150)
- Use HTTPS URLs in pom.xml (#151)
- Use mvn batch mode (#148)
- Message env var is not available in pipeline jobs (#143)
- Ensure default values are used for build parameters when triggering builds (#138)
- Support Boolean Parameters (#135)
- Issue #133: Message properties should do variable substitution on entire set of properties, not by line. (#136)
- Support Multi-line String parameter for CI_MESSAGE definition
(#124)
- Fixes JENKINS-57642
- Ensure timestamp is set when sending FedMsg (#131)
- add pipeline syntax support for CIBuildTrigger (#106)
- waitForCIMessage does not work correctly with message checks (#114)
- sendCIMessage gets stuck running when given nonexistent provider (#116)
- "CI event" build trigger keeps creating threads on Jenkins when given invalid client name (#118)
- Give users some sort of notification when a trigger has a fatal error (#121)
- Trigger on multiple topics. (#111)
- Fix pipeline snippet generator (#113)
- Fix fedmsg topic override problem and test (#108)
- Bump jackson-databind to address security issues (#105)
- getMsgId() for Fedmsg in jms-messaging plugin discrepancy. (#103)
-
Ensure only admins can perform testConnection() (#104)
-
The jms-messaging-plugin defaults to org.fedoraproject if no topic override is specified (#101)
-
Trigger thread is dying with an unhandled exception. (#100)
-
Do not override PATH variable (#88)
-
Fix defaults to work. Remove obsolete code. Some general cleanup. (#87)
-
MESSAGE_HEADERS should include all message headers. (#82)
-
Update pom to new parent and fix deps (#86)
-
MESSAGE_HEADERS should include all message headers. (#83)
-
Change provider selection to use a dropdownDescriptorSelector. (#79)
- Correct possible empty CI_MESSAGE using ActiveMQ.
Breaking change
WARNING: Version 1.0.39 no longer supports a JMS selector for the FedMsg Messaging Provider. You must update your jobs to add a Message Check to specify what you want to trigger on.
- Fully implement message checks for AMQ messages.
- Remove JMS selector and message properties from Fedmsg messages.
- Only support JSON path for all message checks.
- Fix issue where plugin was overwriting CI_MESSAGE while jobs are queued.
- not released
- not released
- Support global node properties in topics names for triggers (#62)
- Force trigger thread to be stopped on trigger removal, project disable, and project delete. (#61)
- Add @Whitelisted to MessagingProviderOverrides constructor. (#60)
- Update CIMessageSendStep code to use CIMessageNotifier. Add methods to allow calls from pipeline code.
- Improve interrupt waitforcimessage (#51)
- add extra logging for waitForCIMessage (#50)
- Fix SendResult to not require it to be Serializable
- sendCIMessage now returns SendResult (#48)
- Add msgchecks to waitForMsg and fix timeout (#47)
- added MsgCheck equals() to fix thread restart issue.
- Add support for JsonPath in MessageChecks (only FedMsg)
- Fix trigger thread not being restarted on JMS messaging provider change.
- Fix width of topic text boxes for overrides
- Add ability to use queues in AMQ messaging provider. (#38)
- <not released>
- Rework to support quick and frequent stop/start of triggers with properties in Multibranch jobs
-
Do not block Jenkins load when previous plugin's ancestor's descriptor has been detected.
-
Improve interpolation of environment variables in messages
-
Add logging for pipeline steps
-
Add failOnError support for sending messages
-
Add support for replacing tokens using previously defined properties
-
Refactor pipeline steps so logging and aborting works properly.
-
fix missing fillProviderMethod for waitForCIMessage
-
fix NPE for GlobalCIConfiguration.getFirstProviderOverrides
- Improve interruptions of connection threads by ensuring that provider is connected before trying to interrupt and join trigger thread.
- Add topic provider.
- Fix Tests for new selections
- Variable expansion now supported for override topics.
- (ActiveMQ) Improve resiliency by better cleanup failed connections.
- Upgrade ActiveMQ client to version 5.14.5.
- Allow a job to re-subscribe if job was previously disabled.
- Fix migration steps to ensure null providers are fixed on startup.
- Fix for double-quotes in FedMsg selectors
- Add MESSAGE_HEADERS to the env for triggered jobs.
- Allow topic configuration at build steps
- (JENKINS-42401) Enable trigger to work with Pipeline jobs
- Added Message Check support.
- Deleting project does not unsubscribe job nor shutdown subscriber thread.
- Renaming project does not stop/start subscriber thread.
- Correct migration bug when plugins are installed that implement SaveableListener.
- Improve persistence of Keystore and Truststore config values.
- Support variable expansion in Keystore and Truststore config values.
- Introduction of SSL Certificate Authentication for ActiveMQ.
- FedMsg Message Provider
- Supports triggering
- Supports sending and receiving
- Signing of messages not yet implemented.
- Remove un-necessary dependencies
- Reduce required version of Jenkins Core
- Fix startup crash for project types Project and MatrixProject
- Initial release