Your first stop for learning how to get started with Jira Service Management.
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 the integration offer?
Use 's Integration to forward build alerts to . 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.
How does the integration work?
When a build alert is created in , an alert is created in automatically through the integration.
Set up the integration
is an API-based integration. Setting it up involves the following steps:
Add a integration in
Configure the integration in
Add a Codeship integration
To add a integration in , complete the following steps:
Go to your team’s operations page.
On the left navigation panel, select Integrations and then Add integration.
Run a search and select “”.
On the next screen, enter a name for the integration.
Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.
The integration is saved at this point.
Expand the Steps to configure the integration section and copy the API URL.
You will use this URL while configuring the integration in later.
Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.
Configure the integration in Codeship
To configure the integration of with , complete the following steps:
Go to Project Settings > Notifications.
Select Add > New notification.
Paste the API URL copied previously from into URL.
Select the events you want to trigger notifications.
Specify the branch for filtering, if needed.
You can add more rules to an existing branch (or branch match). To remove specific rule trigger for notifications, either disable it (use the toggle) 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. Also, 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 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