Files
brew/docs/BrewTestBot.md
T
Mike McQuaid cf47983e13 Remove docs remote theme usage
- Avoid `jekyll-remote-theme` so docs builds use local shared files.
- Reference canonical `brew.sh` theme assets instead of copying them here.
- Keep only the layouts and includes needed by the docs site.
- Point shared docs page images at `brew.sh` for HTML-Proofer.
- Render the install demo GIF at retina size in the README.
2026-06-08 11:59:00 +01:00

1.4 KiB

logo, image, redirect_from, last_review_date
logo image redirect_from last_review_date
https://brew.sh/assets/img/brewtestbot.png https://brew.sh/assets/img/brewtestbot.png
/Brew-Test-Bot
2025-02-08

BrewTestBot

brew test-bot is what runs the automated review and testing system funded by our Kickstarter in 2013.

It comprises three Mac Pros hosting virtual machines, several Intel and M1 Mac minis and some cloud Ubuntu instances that run the test-bot.rb command to perform bottle builds and automated testing of the full lifecycle of any change to Homebrew or its taps.

Pull Requests

The bot automatically builds pull requests and updates their status depending on the result of the job.

For example, a job which has been queued but not yet completed will have a section in the pull request that looks like this:

Triggered Pull Request


A failed build looks like this:

Failed Pull Request


A passed build that's been approved to merge looks like this:

Passed Pull Request


On failed or passed builds you can click the "Details" link for each check to view its output in GitHub Actions.