CI/CD Maintainers

Fix failed PRs in no time

The CI/CD Maintainers are AI Teammates that automatically review your engineers' failed pull requests and help you fix them.

Automatic Detection of Failed PRs

AI Teammates are automatically alerted when a PR fails CI.

Root Cause Analysis

Immediately get to the heart of the issues that caused CI to fail.

Codebase-aware AI Teammates

AI Teammates understand your codebase and use it as context.

Solutions Within Seconds

Get actionable feedback that you can implement to fix your code.

Private & Secure

As with all Kubiya use cases, your AI Teammates maintain your org's security and information protection.

Want to get started?

Prerequisites

• A Kubernetes cluster

• A Kubiya runner (if you haven't already, you can create this during the use-case setup flow)

• A GitHub personal access token with access to each of the relevant repositories (see permissions)

  • The token should be saved as a Kubiya secret called GH_TOKEN

• A Slack integration (the Kubiya Slack app)

• A Slack channel in which Kubiya Slack app is added

Set up the CI/CD Maintainers use case

1. Go to the New Use Cases page

2. Select CI/CD Maintainers and click Continue

3. Follow the on-screen instructions

   1. If you haven't created a runner yet, no problem. In the Select Runner drop-down, choose Create a Runner and follow the on-screen instructions.

   2. Make sure the Slack channel you provide is one in which the Kubiya Slack app has been added

4. Click Save and Continue. Behind the scenes this is running Terraform Plan.

5. If the plan is successful, you'll be brought to a screen showing a summary of the resources that will be created. To finish setup, click Delegate. This will run a Terraform Apply.

6. Refresh the screen and check that the use case's status is Active. If so, then the Terraform Apply was successful and you are ready to use your use case.

Permissions & Access

For this use case, Kubiya requires specific permissions in your GitHub.

To do so, create a fine-grained personal access token in GitHub. This token should have access to all of the repositories in which your AI Teammates will operate.

Here are the specific permissions that should be granted:

• Actions: Read and Write

• Commit statuses: Read-only

• Contents: Read-only

• Issues: Read and Write

• Metadata: Read-only

• Pull requests: Read and Write

• Webhooks: Read and Write

• Workflows: Read and Write

For your GitHub token, make sure that under Resource owner you've selected the correct GitHub organization.

How to use your AI Teammates

Now that you've set up the CI/CD Maintainers, your AI Teammates will spring into action automatically whenever a PR fails CI.

Upon this happening, you will receive a notification in Slack that your AI Teammate is getting to work.

The AI Teammate will post a comment on the PR itself in GitHub with the root cause analysis and resolutions to fix your code.