Your first stop for learning how to get started with Jira Service Management.
What does the integration offer?
Use 's Integration to forward alerts to . acts as a dispatcher for these alerts and determines the right people to notify based on on-call schedules– notifies via email, text messages (SMS), phone calls, and iPhone & Android push notifications, and escalates alerts until the alert is acknowledged or closed.
How does the integration work?
When the status of a project is failing, broken, or errored on , an alert is created in automatically through the integration.
When the status is passed or fixed on , the alert is closed in .
Set up the integration
is an API integration. Setting it up involves the following steps:
Add a integration in
Configure the integration in
Add a Travis CI 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 webhook URL.
You will use this key 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 Travis CI
To configure the integration of with , complete the following steps:
Activate the service hook for Travis CI on Github by selecting the Github repositories to monitor.
Add the .travis.yml file to the repository.
Add the following configuration to the .travis.yml file.
Paste the webhook URL copied previously into webhooks.
Commit the .travis.yml file to the root of the repository.
The requestbin.com URL in the following payload can be generated from RequestBin.com. You can use the service to create a free HTTPS endpoint. Any HTTP requests sent to that endpoint will be recorded with the associated payload and headers so you can observe the data sent from our webhooks before configuring your application to accept it.