v0.4.0

[0.4.0] - 2024-1-04

Fixed

• If you were using Rubygem with version >= 3.4.0, CI Runner would not run when
  Rake was not activated in your Gemfile.

Add support for Buildkite

Add support for Buildkite

🎉 CI Runner can now rerun test failures that happened on Buildkite.

• For public builds, no access token is required.
• For private builds, you'll need to store a buildkite personal access token in your config. Added the ci_runner github_token command which will help you create a token in a couple of clicks.

CI Runner will now let you know if your version is outdated

Add support for Circle CI

🎉 Circle CI user can now use CI Runner.

CI Runner will now let you select failed Circle CI build. Downloading a CircleCI log output requires an authentication token for private builds.
Added the ci_runner circle_ci_token TOKEN to store a token in your configuration.

Changed

• CI Runner will now tell you if it fails to find test failures from the log output.
• CI Runner will only allow failed CI checks to be selected. Previously, users could select
  check that were cancelled, timed out etc...

Fixed

• Fixed log detection for output that have ANSI colors (\e[31m Blabla)

First release of CI runner

🎉 Hello world!

CI Runner is a tool to help rerun failures from a CI onto a local machine without having to copy paste log output on your terminal.

❓ Confused?

A regular workflow in developers day to day life is to write code, run tests related to what changed and then push to see if the whole test suite passes. If your CI fail, you most likely will copy the path of the file and the name of the test to rerun those on your machine. Rinse and repeat for all failures.

CI Runner will automate this workflow by downloading the log output from a CI provider (GitHub currently only supported), parse it, detect failures and rerun only the tests that failed on CI.

🌞 Features

• Interactively ask which CI you want to rerun if your project has multiple CI
• Automatically detect the Ruby version and use it if your machine has it installed
• Automatically defect which Gemfile to use (in case your project is tested with multiple Gemfiles)
• Works with Minitest and RSpec
• Work on many projects without configuration, but you can configure it CI Runner can't detect test failures on your project.