Notice: FlyCI macOS runners will be discontinued effective September 30th, 2024.

Read more
See all blog posts

announcement

FlyCI Wingman - your AI solution for failing CI builds

Save time, boost productivity, and increase developer satisfaction with seamless integration and automated error detection

VRVeselina Radeva
Introducing FlyCI Wingman - Now Available

Continuous integration (CI) is crucial for maintaining top-notch software. Making minor code changes via pull requests ensures your code stays clean and efficient. Adding checks in GitHub Actions when a pull request is opened or changed enforces coding standards, runs automated tests, and ensures your code works across different platforms. However, CI builds can fail, disrupting developers' workflow and making debugging a frustrating and time-consuming task.

Pain points of failing CI builds

Developers prefer to avoid switching focus from valuable and exciting work. Here are the main challenges they face with failing CI builds:

  • Disruption: Frequent CI build failures disrupt developers' focus and workflow.
  • Time-consuming: Troubleshooting failures can trap a developer in a fix-commit-build loop for hours.
  • Delayed Product development: Persistent CI failures slow down the progress of the product and impact release timelines.
  • Frustration and Burnout: Constant failures can lead to frustration and burnout, reducing motivation and productivity.

We developed FlyCI Wingman to ease developers' day-to-day work and solve these pain points.

Introducing FlyCI Wingman

FlyCI Wingman is an AI-powered agent designed to tackle developers' challenges when dealing with failing CI builds. It analyzes failure logs and provides fixes in the form of code suggestions directly to your pull request. Then, it's up to the pull request owner to review and merge the changes to the code base. Here's how FlyCI Wingman helps:

  • Minimizes Interruptions: Developers, when FlyCI Wingman auto-healing is enabled, practically eliminate the need to deal with failing builds.
  • Saves Time: FlyCI Wingman handles troubleshooting and bug-fixing on behalf of developers.
  • Boosts Development Speed: Developers can now focus on creating features and value, not debugging.
  • Increases Developers Satisfaction: Less time spent in debugging means happier, more motivated developers.

Let's dive deeper into how FlyCI Wingman works.

How FlyCI Wingman solves CI build failures

FlyCI Wingman addresses CI build failures with several core features.

Automated Error Detection

FlyCI Wingman runs within FlyCI runners and uses a language model (LLM) trained to fix failing builds. It analyzes failure logs and suggests code fixes, leaving developers to review and merge the code changes.

Read more details on how FlyCI Wingman works.

Seamless Integration

Integrating FlyCI Wingman with GitHub Actions is quick and easy. Just install the GitHub app, configure the GitHub Actions workflow runners, and re-run a failing build with AI via the FlyCI Dashboard.

A detailed step-by-step guide is available later in this post and in the documentation.

Smart Issue Resolution

Enable self-healing CI builds by adding wingman label to the workflow's runs-on configuration. This eliminates the need for developers to re-run the failing builds with AI from the FlyCI Dashboard.

Benefits of Using FlyCI Wingman

Beyond resolving CI pain points, FlyCI Wingman offers additional benefits like:

  • Efficient teams: With less time spent debugging and fewer context switches, the team's overall efficiency improves.
  • Faster Release Cycles: Improved development speed results in quicker releases.
  • Improved Code Quality: FlyCI Wingman suggests fixes that adhere to the best practices for writing software, thus improving code quality.
  • Cost Savings: Faster value delivery to customers translates to cost savings.

Getting started with FlyCI Wingman

Quick Setup Guide

Setting up FlyCI Wingman is simple. Follow the quick setup (estimated time: 5 minutes).

  • Install the FlyCI GitHub app↗ if you haven't done it yet and give it access to your repository.
  • Use FlyCI macOS runners in your workflow by updating the runs-on configuration with any of the available runner labels.
  • Add the wingman label to the runs-on configuration to enable auto-healing of your failing builds
jobs:
  test:
    name: Make my build green 🚀
    runs-on: [flyci-macos-14-m2, wingman]
    steps: ....

Detailed guide on how to use FlyCI Wingman.

Support and Resources

For additional information and support, visit the links below:

Report an issue

To report an issue with FlyCI runners or FlyCI Wingman, contact us at contact@flyci.net.

Join our Discord server↗ to reach out directly to the FlyCI team.

Why choosing FlyCI Wingman?

Better focus

Shift your attention to innovating in your product instead of troubleshooting failing builds.

Save time

Automatically fix CI builds, reducing debugging time. FlyCI Wingman is doing the fixes for you.

Automated fixes

Automatically get fixes for failing GitHub Actions workflows directly proposed in your pull request.