Learn how to configure your profile, get notifications from Opsgenie and view on-call schedules.
The practice of continuous integration involves repeated automated testing and code merging with notifications to alert developers to problems in their code in real time. combines this with the practice of continuous delivery, which provides for regular code deployment once changes have passed automated tests. Essentially, when code is pushed to GitHub (or Bitbucket), rebuilds your application on its secure servers and runs your automated tests. If the tests fail, it notifies your development team via email or integration.
What does Opsgenie offer Codeship users?
Use Integration to forward build alerts to . Opsgenie
determines the right people to notify based on on-call schedules– notifies via email, text messages (SMS), phone calls, and iOS & Android push notifications, and escalates alerts until the alert is acknowledged or closed.
Functionality of the integration
When a build alert is created in , an alert is created in automatically through the integration.
Add Codeship Integration to Opsgenie
Go to . Search for and select Add.
Specify who is notified of alerts using the Responders field. Auto-complete suggestions are provided as you type.
Select Save Integration.
Configuration in Codeship Pro
Configuring Build Notifications
To configure build notifications in , go to Project Settings and click on the Notifications tab.
To add more rules to an existing branch (or branch match), click add to the right of the branch name. To add rules for a new branch (or branch match), click the big new notification button at the bottom of the page.
To remove specific rule trigger for notifications, either disable it (use the toggle on the right-hand side) or delete it completely.
All rules apply to either “All Branches”, a names branch, or a branch match. If the field is left empty, the rule applies to all branches.
Additionally, all rules can select between started, failed, succeeded, and recovered as events that trigger a notification. Select at least one event in order to save the rule.
started -> sends a notification when a new build is triggered
failed -> sends a notification if a build fails for some reason
succeeded -> sends a notification if the build finishes successfully
recovered -> sends a notification if the previous build failed, but the current build succeeded
sends build data using Webhook Services
Sample Webhook Message from Opsgenie Codeship Plugin
The status field has one of the following values:
initiated for newly started build
error for failed builds
success for passed builds
stopped for stopped builds
waiting for waiting builds
ignored for builds ignored because the account is over the monthly build limit
blocked for builds blocked because of excessive resource consumption
infrastructure_failure for builds which failed because of an internal error on the build VM