Jenkins is an open source automation server. It helps automate the parts of software development related to building, testing, and deploying, facilitating continuous integration and continuous delivery
AlertOps’ alert management system can be integrated with Jenkins to receive and respond to all (predefined status mappings) job/build alerts through email, SMS, push notification or phone alerts. AlertOps would ensure that the alert/job status would reach the appropriate team by using proper workflows, escalation policies and schedules. Based on your ruleset, incidents can be automatically opened and closed, depending on whether Jenkins sends a job/build success or failure (any status update throughout the entire flow for that matter).
The above scenario and scope for integration is due to the fact that AlertOps has a very flexible and simple API/Webhook configuration feature that can be leveraged with Jenkins’ notification plugin.
You can send alerts from Jenkins to AlertOps.
- AlertOps will automatically create an incident when a new alert is received from Jenkins when the build^status field contains any other value other than ‘SUCCESS’. (Note: We give this definition because, ideally, we would want any event from Jenkins to be alerted to a team, to take specific action until it is fully succeeded. The events that come in, come with phase variable values finalized, completed, started, queued)
- If an alert matches an existing Open Alert (based on the source ID), AlertOps will recognize the new alert as part of the existing alert and ignore the alert (you can configure this).
- The alert will be recorded in the Inbound Messages table as “Mapped Appended.”
- AlertOps will automatically close the same incident when an alert with build^status contains “SUCCESS”
These are examples of just some of the things you can do with Jenkins and AlertOps.
