Travis CI

Overview

This document provides a detailed guide to integrating Travis CI with Callgoose SQIBS for real-time Incident Management, Incident Auto Remediation, Event-Driven Automation, and other automation purposes. The integration enables automatic creation, updating, and resolution of incidents in Callgoose SQIBS based on alerts triggered in Travis CI. The guide includes steps for setting up alerts in Travis CI, configuring webhook notifications, creating API filters in Callgoose SQIBS, and troubleshooting.

Prerequisites

• Travis CI Account: Access to Travis CI for creating alerts and managing notifications.
• Callgoose SQIBS Account: With valid privileges to set up API filters and receive notifications.
• Webhook/API Endpoint: Available in Callgoose SQIBS to receive alerts from Travis CI.

1. Obtain API Token and Endpoint Details

To integrate with Callgoose SQIBS, you first need to obtain an API token and find the API endpoint details.

1. Generate an API Token:

• Follow the guide on How to Create API Token in Callgoose SQIBS.

1. Find the API Endpoint:

• Refer to the Callgoose SQIBS API Endpoint Documentation to get the endpoint details where the JSON payloads from Travis CI will be sent.

2. Debugging and Troubleshooting

You can enable debugging in the API tokens used with Travis CI notifications for troubleshooting purposes.

• Enable Debugging:
• You can update the debug value when adding or updating an API token.
• When API tracking is enabled, logs are stored in the API log section for your review. The debugging option will automatically disable after 48 hours.
• When API tracking is turned off, no logs are saved in the API log.
• Using API Log for Troubleshooting:
• The API log provides detailed information on all API calls made to Callgoose SQIBS.
• You can check the JSON values in each API log entry for troubleshooting purposes.
• Use the information in the API log to create or refine API filters to ensure incidents are created correctly based on the API payloads received.
• Callgoose SQIBS creates incidents according to your API filter configuration, giving you full control over how alerts from different services trigger incidents and alerts for your support team or automation processes.

3. Configuring Travis CI to Send JSON Payloads

To configure Travis CI to generate the JSON payloads similar to the examples provided, follow the steps outlined below. These steps will guide you through setting up the necessary alerts and webhook notifications within Travis CI to ensure that the JSON payloads match those expected by Callgoose SQIBS.

3.1 Setting Up Notifications in Travis CI

To generate the required JSON payloads, you first need to set up notifications within Travis CI.

1. Log in to the Travis CI Console:

• Access the Travis CI platform using your account credentials.

1. Navigate to the Notification Settings:

• In the Travis CI console, go to Settings > Notifications.

1. Configure Webhook Notifications:

• Choose Webhook as the notification method to send data to a webhook.
• Enter the webhook URL provided by Callgoose SQIBS.

3.2 Configuring the Webhook Notification

To ensure that the JSON payload sent matches the examples provided, follow these steps when configuring the webhook:

1. Add Webhook URL:

• In the Webhook URL field, enter the endpoint provided by Callgoose SQIBS.
• Ensure the protocol is HTTPS for secure data transmission.

1. Customize Payload Format:

• Ensure that the payload includes key fields like "status", "build_id", "repository", "branch", "commit" and others as shown in the example payloads.

1. Example Payload Setup:

json

{
  "status": "failed",
  "build_id": "12345",
  "repository": "your-repo-name",
  "branch": "main",
  "commit": "a1b2c3d4e5"
}

1. Placeholder Explanation:

• "status": Replaces with the status of the build (e.g., success, failed).
• "build_id": A unique identifier for the build.
• "repository": The name of the repository.
• "branch": The branch where the build was triggered.
• "commit": The commit hash associated with the build.

1. Test the Webhook Configuration:

• Before activating the webhook, perform a test to ensure that the JSON payload is correctly formatted and is being sent to the Callgoose SQIBS API endpoint as expected.
• Review the payload in Callgoose SQIBS to confirm that it matches the expected structure.

4. Configuring Callgoose SQIBS

4.1 Create API Filters in Callgoose SQIBS

To correctly map incidents from the Travis CI events, you need to create API filters based on the JSON payloads received.

4.1.1 Example JSON Payloads from Travis CI

Build Failed (status: "failed")

json

{
  "status": "failed",
  "build_id": "12345",
  "repository": "your-repo-name",
  "branch": "main",
  "commit": "a1b2c3d4e5"
}

Build Succeeded (status: "success")

json

{
  "status": "success",
  "build_id": "12345",
  "repository": "your-repo-name",
  "branch": "main",
  "commit": "a1b2c3d4e5"
}

4.2 Configuring API Filters

4.2.1 Integration Templates

If you see a Travis CI integration template in the "Select Integration Template" dropdown in the API filter settings, you can use it to automatically add the necessary Trigger and Resolve filters along with other values. The values added by the template can be modified to customize the integration according to your requirements.

4.2.2 Manually Add/Edit the Filter

Trigger Filter (For Creating Incidents):

• Payload JSON Key: "status"
• Key Value Contains: ["failed"]
• Map Incident With: "build_id"
• This corresponds to the unique build_id from the Travis CI payload.
• Incident Title From: "repository"
• This will use the repository name as the incident title in Callgoose SQIBS.
• Incident Description From: Leave this empty unless you want to use a specific key-value from the JSON payload. If a key is entered, only the value for that key will be used as the Incident Description instead of the full JSON. By default, the Incident Description will include the full JSON values.

Resolve Filter (For Resolving Incidents):

• Payload JSON Key: "status"
• Key Value Contains: ["success"]
• Incident Mapped With: "build_id"
• This ensures the incident tied to the specific build_id is resolved when the build status returns to normal.

Refer to the API Filter Instructions and FAQ for more details.

4.3 Finalizing Setup

1. Save the API Filters:

• Ensure that the filters are correctly configured and saved in Callgoose SQIBS.
• Double-check that all key mappings, incident titles, and descriptions are correctly aligned with the payload structure sent by Travis CI.

1. Test the Integration:

• Manually trigger a build failure in Travis CI to test if incidents are created in Callgoose SQIBS.
• Verify that the incident appears in Callgoose SQIBS with the correct title, description, and mapped values.
• Trigger a successful build in Travis CI and ensure that the corresponding incident in Callgoose SQIBS is marked as resolved.

5. Testing and Validation

5.1 Triggering Alerts

1. Simulate a Build Failure:

• Trigger a condition in Travis CI that causes a build to fail (e.g., introduce a syntax error in the code).
• Verify that an incident is created in Callgoose SQIBS with the correct information.

5.2 Resolving Alerts

1. Fix the Build Issue:

• Correct the issue in the code and trigger a successful build in Travis CI.
• Verify that the incident in Callgoose SQIBS is automatically marked as resolved.

6. Security Considerations

• API Security: Ensure that the Callgoose SQIBS API endpoint is correctly configured and that the API token is securely stored and used.
• Travis CI Permissions: Confirm that the webhook in Travis CI has appropriate permissions to send alerts and data to Callgoose SQIBS.
• Data Encryption: Ensure that the transmission of data between Travis CI and Callgoose SQIBS is encrypted, especially if sensitive information is involved.

7. Troubleshooting

• No Incident Created: If no incident is created, verify that the webhook URL in Travis CI is correct and that the JSON payload structure matches the API filters configured in Callgoose SQIBS.
• Incident Not Resolved: Ensure that the resolve filter in Callgoose SQIBS is correctly configured and that the JSON payload sent by Travis CI matches the expected structure.
• Webhook Not Triggering: Check the webhook settings in Travis CI to ensure it is enabled and correctly configured to send notifications.
• API Token Issues: Verify that the API token in Callgoose SQIBS is active and correctly set up to accept the incoming payloads.
• Payload Formatting Errors: Use the API log in Callgoose SQIBS to inspect the incoming payloads for any formatting errors or discrepancies that might prevent the filters from matching.

8. Conclusion

This guide provides a comprehensive overview of how to integrate Travis CI with Callgoose SQIBS for effective incident management. By following the steps outlined, you can ensure that alerts from Travis CI are automatically reflected as incidents in Callgoose SQIBS, with proper resolution tracking when the issues are resolved.

For further customization or advanced use cases, refer to the official documentation for both Travis CI and Callgoose SQIBS:

• Travis CI Documentation
• Callgoose SQIBS API Token Documentation
• Callgoose SQIBS API Endpoint Documentation
• API Filter Instructions and FAQ
• How to Send API

This documentation will guide you through the integration process, ensuring that your incidents are managed effectively within Callgoose SQIBS based on real-time alerts from Travis CI.